← previous blocknext block →recent activity
Analyzing
Block #96,306,842
17 transactions · 17 stateful · 2026-08-15 21:08:07 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,306,842 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000f
0x78999c…f371
16 touches
28 conflicts
0x00000000…000b
0x754704…b603
16 touches
28 conflicts
0xe0659a3f…90d9
0x000000…a032
16 touches
28 conflicts
0x34b1e500…7687
0x754704…b603
16 touches
28 conflicts
0x00000000…000b
0x78999c…f371
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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: 0x78999cc9…3cf371
28 conflicts on slot 0x0000000000…00000f
Audit this contract →
← previous block·next block →recent activity