← previous blocknext block →recent activity
Analyzing
Block #96,268,336
13 transactions · 13 stateful · 2026-08-15 17:54:27 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,268,336 · 13 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
2w03w14w26w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd646da5d…7746
0x968279…9342
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x922afba5…d9cc
0x968279…9342
6 touches
3 conflicts
0x922afba5…d9cd
0x968279…9342
6 touches
3 conflicts
0x922afba5…d9cf
0x968279…9342
6 touches
3 conflicts
0xd646da5d…773f
0x968279…9342
6 touches
3 conflicts
0xd646da5d…7740
0x968279…9342
6 touches
3 conflicts
0xd646da5d…7743
0x968279…9342
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: 0x96827978…f09342
3 conflicts on slot 0xd646da5d44…1e7746
Audit this contract →
← previous block·next block →recent activity