← previous blocknext block →recent activity
Analyzing
Block #96,696,253
14 transactions · 13 stateful · 2026-08-17 05:46:58 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,696,253 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2196604…5c35
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x2d3930d3…c9b8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4183e693…4175
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0x92eaab4e…f5da
0x065c9d…c394
2 touches
0 conflicts
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
3 conflicts on slot 0xd2196604a8…1e5c35
Audit this contract →
← previous block·next block →recent activity