← previous blocknext block →recent activity
Analyzing
Block #94,051,319
9 transactions · 9 stateful · 2026-08-07 23:30:01 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,051,319 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x17abd0b1…f478
0x34b655…2a6f
4 touches
1 conflict
0xcf005309…1129
0x34b655…2a6f
4 touches
1 conflict
0xd08098a8…f0a6
0x34b655…2a6f
4 touches
1 conflict
0xe66201d4…84f1
0x34b655…2a6f
4 touches
1 conflict
0xfb874a6c…caa0
0x34b655…2a6f
4 touches
1 conflict
0x2a34bb88…04d6
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c6f
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity