← previous blocknext block →recent activity
Analyzing
Block #94,836,925
13 transactions · 12 stateful · 2026-08-10 17:38:46 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,836,925 · 13 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
1w03w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x61660086…7461
0x065c9d…c394
4 touches
1 conflict
0xc72a0887…45fd
0x065c9d…c394
3 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x22c4a7c1…aa2c
0x065c9d…c394
2 touches
0 conflicts
0x3e002e09…4ac9
0x065c9d…c394
2 touches
0 conflicts
0xa4f80979…4d71
0x065c9d…c394
2 touches
0 conflicts
0xac422216…b9bb
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity