← previous blocknext block →recent activity
Analyzing
Block #94,252,899
12 transactions · 9 stateful · 2026-08-08 16:29:17 UTC
Parallelism
75/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,252,899 · 12 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x6cef802b…436f
0x065c9d…c394
2 touches
0 conflicts
0xc3edbf08…6ce8
0x065c9d…c394
2 touches
0 conflicts
0xcfd1b221…eeae
0x065c9d…c394
2 touches
0 conflicts
0xde307c90…9c35
0x065c9d…c394
2 touches
0 conflicts
0xe88fde4c…f3b1
0x065c9d…c394
2 touches
0 conflicts
0xe9494446…e6a5
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