← previous blocknext block →recent activity
Analyzing
Block #96,666,737
30 transactions · 24 stateful · 2026-08-17 03:18:31 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,666,737 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w39w010w111w112w213w314w020w421w522w123w225w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10abefc9…c9bc
0x2b46c0…1669
8 touches
6 conflicts
0x10d80fee…dbda
0x2b46c0…1669
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x2491d756…b71c
0xa6afd3…d132
8 touches
6 conflicts
0x6847107a…f468
0xa6afd3…d132
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
8 touches
6 conflicts
0x40970e69…da50
0x2b46c0…1669
8 touches
6 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
8 touches
6 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: 0x2b46c08c…ec1669
6 conflicts on slot 0x10abefc9eb…c5c9bc
Audit this contract →
← previous block·next block →recent activity