← previous blocknext block →recent activity
Analyzing
Block #96,535,267
16 transactions · 15 stateful · 2026-08-16 16:17:17 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,535,267 · 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
2w03w17w08w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7197c2c…c148
0x968279…9342
14 touches
21 conflicts
0x521a5982…a82a
0x754704…b603
14 touches
21 conflicts
0x00000000…0006
0x968279…9342
14 touches
21 conflicts
0x9c96d45c…c82a
0x968279…9342
14 touches
21 conflicts
0x9c96d45c…c82b
0x968279…9342
14 touches
21 conflicts
0x9c96d45c…c82e
0x968279…9342
14 touches
21 conflicts
0x9c96d45c…c82f
0x968279…9342
14 touches
21 conflicts
0x9c96d45c…c831
0x968279…9342
14 touches
21 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
21 conflicts on slot 0xd7197c2c05…c7c148
Audit this contract →
← previous block·next block →recent activity