← previous blocknext block →recent activity
Analyzing
Block #96,352,177
10 transactions · 9 stateful · 2026-08-16 00:56:07 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,352,177 · 10 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
2w03w16w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x939bbb96…8556
0x34b655…2a6f
4 touches
1 conflict
0xc3fc40da…1c60
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xeca3f7cd…57b6
0x34b655…2a6f
4 touches
1 conflict
0xeca3f7cd…57b7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
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 0x939bbb9652…608556
Audit this contract →
← previous block·next block →recent activity