← previous blocknext block →recent activity
Analyzing
Block #96,045,393
17 transactions · 15 stateful · 2026-08-14 23:13:06 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,045,393 · 17 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
6w07w18w29w310w411w512w613w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32df96aa…ce80
0x968279…9342
14 touches
21 conflicts
0x3e6cf58d…0e13
0x968279…9342
14 touches
21 conflicts
0x3e6cf58d…0e14
0x968279…9342
14 touches
21 conflicts
0x3e6cf58d…0e17
0x968279…9342
14 touches
21 conflicts
0x3e6cf58d…0e18
0x968279…9342
14 touches
21 conflicts
0x3e6cf58d…0e1a
0x968279…9342
14 touches
21 conflicts
0x32df96aa…ce7d
0x968279…9342
14 touches
21 conflicts
0x32df96aa…ce7e
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 0x32df96aa9b…21ce80
Audit this contract →
← previous block·next block →recent activity