← previous blocknext block →recent activity
Analyzing
Block #94,912,556
18 transactions · 18 stateful · 2026-08-10 23:59:10 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,912,556 · 18 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
2w05w06w17w08w19w210w311w413w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d1b66e5…bf3b
0x968279…9342
10 touches
10 conflicts
0x0d1b66e5…bf3e
0x968279…9342
10 touches
10 conflicts
0x63606de7…8596
0x968279…9342
10 touches
10 conflicts
0x63606de7…8597
0x968279…9342
10 touches
10 conflicts
0x63606de7…859a
0x968279…9342
10 touches
10 conflicts
0x63606de7…859b
0x968279…9342
10 touches
10 conflicts
0x63606de7…859d
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 0x0d1b66e59e…90bf3b
Audit this contract →
← previous block·next block →recent activity