← previous blocknext block →recent activity
Analyzing
Block #94,470,411
16 transactions · 15 stateful · 2026-08-09 10:53:44 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,470,411 · 16 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
3w04w15w26w07w18w29w310w411w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x480edc7b…160c
0x065c9d…c394
10 touches
10 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x0778475b…bd75
0x2a68ba…90c5
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xed08ca1d…48bd
0x34b655…2a6f
10 touches
10 conflicts
0x8f361903…8677
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
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: Kuru Exchange: Market-MON/USDC
10 conflicts on slot 0x480edc7b07…69160c
Audit this contract →
← previous block·next block →recent activity