← previous blocknext block →recent activity
Analyzing
Block #94,758,552
22 transactions · 21 stateful · 2026-08-10 11:04:30 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,758,552 · 22 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
1w04w05w16w17w29w010w111w213w315w016w117w218w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x90a66fa7…9014
0x34b655…2a6f
8 touches
6 conflicts
0xb954a95b…d318
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x450fb5b7…9760
0x34b655…2a6f
4 touches
1 conflict
0x508bbf1b…fe95
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity