← previous blocknext block →recent activity
Analyzing
Block #89,840,047
12 transactions · 11 stateful · 2026-07-24 06:01:13 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,840,047 · 12 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
1w04w16w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xa4dc1328…d42d
0x34b655…2a6f
4 touches
1 conflict
0x1e7f3dcf…5d14
0x065c9d…c394
2 touches
0 conflicts
0x4ecaacf7…9b3b
0x065c9d…c394
2 touches
0 conflicts
0x9bfab863…0866
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xbd7c1b9e…1559
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