← previous blocknext block →recent activity
Analyzing
Block #96,372,921
10 transactions · 10 stateful · 2026-08-16 02:40:28 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,372,921 · 10 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
3w04w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19e1da6e…4a72
0x34b655…2a6f
4 touches
1 conflict
0x1cd97124…bea5
0x34b655…2a6f
4 touches
1 conflict
0x5b30a6e6…b249
0x34b655…2a6f
4 touches
1 conflict
0xfd3d8226…d72f
0x34b655…2a6f
4 touches
1 conflict
0xfd3d8226…d730
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xc2a722dc…1ef8
0x34b655…2a6f
4 touches
1 conflict
0xfca416f4…3474
0x34b655…2a6f
3 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
1 conflict on slot 0x19e1da6e1d…454a72
Audit this contract →
← previous block·next block →recent activity