← previous blocknext block →recent activity
Analyzing
Block #94,753,633
14 transactions · 14 stateful · 2026-08-10 10:39:40 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,753,633 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w210w311w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43f810d1…1fc2
0x968279…9342
10 touches
10 conflicts
0x5e5bcbbc…a92f
0x968279…9342
10 touches
10 conflicts
0x5e5bcbbc…a930
0x968279…9342
10 touches
10 conflicts
0x5e5bcbbc…a932
0x968279…9342
10 touches
10 conflicts
0x43f810d1…1fbe
0x968279…9342
10 touches
10 conflicts
0x43f810d1…1fc1
0x968279…9342
10 touches
10 conflicts
0x43f810d1…1fc4
0x968279…9342
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 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
10 conflicts on slot 0x43f810d167…e71fc2
Audit this contract →
← previous block·next block →recent activity