← previous blocknext block →recent activity
Analyzing
Block #96,783,920
16 transactions · 15 stateful · 2026-08-17 13:07:54 UTC
Parallelism
56/100
Blocked
67%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,783,920 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w08w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x78999c…f371
14 touches
21 conflicts
0x00000000…000b
0x754704…b603
14 touches
21 conflicts
0x34b1e500…7687
0x754704…b603
14 touches
21 conflicts
0x00000000…000f
0x78999c…f371
14 touches
21 conflicts
0xe0659a3f…90d9
0x000000…a032
14 touches
21 conflicts
0xba5743c7…21c1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 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: 0x78999cc9…3cf371
21 conflicts on slot 0x0000000000…00000b
Audit this contract →
← previous block·next block →recent activity