← previous blocknext block →recent activity
Analyzing
Block #99,876,125
14 transactions · 13 stateful · 2026-08-28 10:36:12 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,876,125 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w111w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73d35a6e…6abb
0x34b655…2a6f
10 touches
10 conflicts
0x39ccd26a…4654
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x758a0dd5…0f46
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0x73d35a6e30…d06abb
Audit this contract →
← previous block·next block →recent activity