← previous blocknext block →recent activity
Analyzing
Block #94,235,852
13 transactions · 9 stateful · 2026-08-08 15:02:48 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,235,852 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fecfbd8…60c5
0x34b655…2a6f
4 touches
1 conflict
0xd9a2e985…9e28
0x34b655…2a6f
4 touches
1 conflict
0x3651d66e…b5e9
0x34b655…2a6f
4 touches
1 conflict
0x438268c2…c848
0x34b655…2a6f
4 touches
1 conflict
0x438268c2…c849
0x34b655…2a6f
4 touches
1 conflict
0xbfb8c64d…627a
0x34b655…2a6f
3 touches
1 conflict
0x0a299450…2196
0x447d2e…e9f5
2 touches
0 conflicts
0x11492461…40b9
0x447d2e…e9f5
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 0x9fecfbd8dc…c560c5
Audit this contract →
← previous block·next block →recent activity