← previous blocknext block →recent activity
Analyzing
Block #96,306,315
12 transactions · 11 stateful · 2026-08-15 21:05:27 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,306,315 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce7fee98…9717
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x8bc5e535…9bd6
0x968279…9342
8 touches
6 conflicts
0x8bc5e535…9bd7
0x968279…9342
8 touches
6 conflicts
0x8bc5e535…9bda
0x968279…9342
8 touches
6 conflicts
0x8bc5e535…9bdb
0x968279…9342
8 touches
6 conflicts
0x8bc5e535…9bdd
0x968279…9342
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: 0x96827978…f09342
6 conflicts on slot 0xce7fee98c5…239717
Audit this contract →
← previous block·next block →recent activity