← previous blocknext block →recent activity
Analyzing
Block #94,813,156
14 transactions · 13 stateful · 2026-08-10 15:39:11 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,813,156 · 14 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
1w03w15w07w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x154594d5…564e
0x34b655…2a6f
4 touches
1 conflict
0x17bca7cc…643f
0x34b655…2a6f
4 touches
1 conflict
0x28e5dbea…2f7f
0x34b655…2a6f
4 touches
1 conflict
0x54526994…55b2
0x34b655…2a6f
4 touches
1 conflict
0xfc8cc8e1…85f1
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity