← previous blocknext block →recent activity
Analyzing
Block #94,863,189
20 transactions · 18 stateful · 2026-08-10 19:50:53 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,863,189 · 20 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
1w02w07w18w09w110w211w312w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40457fc4…f39d
0x968279…9342
10 touches
10 conflicts
0x40457fc4…f39e
0x968279…9342
10 touches
10 conflicts
0x40457fc4…f3a0
0x968279…9342
10 touches
10 conflicts
0xdad59977…f9a4
0x968279…9342
10 touches
10 conflicts
0xdad59977…f9a5
0x968279…9342
10 touches
10 conflicts
0xdad59977…f9a8
0x968279…9342
10 touches
10 conflicts
0xdad59977…f9a9
0x968279…9342
10 touches
10 conflicts
0xdad59977…f9aa
0x968279…9342
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 0x40457fc479…99f39d
Audit this contract →
← previous block·next block →recent activity