← previous blocknext block →recent activity
Analyzing
Block #94,475,708
17 transactions · 15 stateful · 2026-08-09 11:20:25 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,475,708 · 17 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
2w03w04w16w07w19w210w311w212w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xb0608dfe…083d
0x34b655…2a6f
6 touches
3 conflicts
0x9a74c40b…6f78
0x34b655…2a6f
6 touches
3 conflicts
0x11d9e4df…3add
0x065c9d…c394
5 touches
3 conflicts
0x816d95ca…cf16
0x34b655…2a6f
4 touches
1 conflict
0x81e1b637…2b3b
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
6 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity