← previous blocknext block →recent activity
Analyzing
Block #94,741,293
13 transactions · 12 stateful · 2026-08-10 09:36:49 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,741,293 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x98bcf3c5…ba0a
0x065c9d…c394
2 touches
0 conflicts
0xac13ff22…c628
0x065c9d…c394
2 touches
0 conflicts
0xc3ecbd6f…46ed
0x065c9d…c394
2 touches
0 conflicts
0xc4201933…2f33
0x065c9d…c394
2 touches
0 conflicts
0xd22a5598…a10e
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity