← previous blocknext block →recent activity
Analyzing
Block #94,490,805
17 transactions · 15 stateful · 2026-08-09 12:36:21 UTC
Parallelism
76/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,490,805 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w19w210w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
6 touches
3 conflicts
0x70eec2ed…f791
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xd8717dcc…b019
0x34b655…2a6f
4 touches
1 conflict
0x48315f67…c1a6
0x34b655…2a6f
2 touches
0 conflicts
0x4bc63e86…8fa8
0x34b655…2a6f
2 touches
0 conflicts
0x5890394d…3000
0x34b655…2a6f
2 touches
0 conflicts
0x67d55258…4556
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 0xcc351d6dd2…b1256b
Audit this contract →
← previous block·next block →recent activity