← previous blocknext block →recent activity
Analyzing
Block #94,811,185
20 transactions · 19 stateful · 2026-08-10 15:29:16 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,811,185 · 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
2w03w04w15w26w17w210w111w012w113w214w315w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8f9c622…096c
0x968279…9342
10 touches
10 conflicts
0xb543fb51…f0cf
0x968279…9342
10 touches
10 conflicts
0xb543fb51…f0d0
0x968279…9342
10 touches
10 conflicts
0xb543fb51…f0d2
0x968279…9342
10 touches
10 conflicts
0xe8f9c622…0967
0x968279…9342
10 touches
10 conflicts
0xe8f9c622…0968
0x968279…9342
10 touches
10 conflicts
0xe8f9c622…096b
0x968279…9342
10 touches
10 conflicts
0xe8f9c622…096d
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 0xe8f9c62266…69096c
Audit this contract →
← previous block·next block →recent activity