← previous blocknext block →recent activity
Analyzing
Block #96,610,472
24 transactions · 16 stateful · 2026-08-16 22:35:33 UTC
Parallelism
92/100
Blocked
19%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,610,472 · 24 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
7w010w111w014w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0xfcce949a…507d
0x34b655…2a6f
4 touches
1 conflict
0xf7f6893b…7d2f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x153d1e25…10ea
0x34b655…2a6f
4 touches
1 conflict
0x309ef367…e8a1
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
1 conflict on slot 0x9a36cb2e52…470929
Audit this contract →
← previous block·next block →recent activity