← previous blocknext block →recent activity
Analyzing
Block #94,858,016
11 transactions · 10 stateful · 2026-08-10 19:24:52 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,858,016 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca32fb2f…669d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x6b47245e…a342
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xca32fb2f2a…59669d
Audit this contract →
← previous block·next block →recent activity