← previous blocknext block →recent activity
Analyzing
Block #94,474,300
15 transactions · 13 stateful · 2026-08-09 11:13:20 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,474,300 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xd1d4b611…00e1
0x34b655…2a6f
4 touches
1 conflict
0xde506f3e…383e
0x065c9d…c394
3 touches
1 conflict
0x7e5ea60a…c4a1
0x34b655…2a6f
2 touches
0 conflicts
0x9c38ffb5…b28e
0x34b655…2a6f
2 touches
0 conflicts
0xa124184b…1dcb
0x34b655…2a6f
2 touches
0 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: Perpl
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity