← previous blocknext block →recent activity
Analyzing
Block #96,535,957
7 transactions · 7 stateful · 2026-08-16 16:20:45 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,535,957 · 7 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
1w02w13w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c1dcb68…a956
0x968279…9342
4 touches
1 conflict
0x5c1dcb68…a94f
0x968279…9342
4 touches
1 conflict
0x5c1dcb68…a950
0x968279…9342
4 touches
1 conflict
0x5c1dcb68…a953
0x968279…9342
4 touches
1 conflict
0x5c1dcb68…a954
0x968279…9342
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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: 0x96827978…f09342
1 conflict on slot 0x5c1dcb68c9…94a956
Audit this contract →
← previous block·next block →recent activity