← previous blocknext block →recent activity
Analyzing
Block #84,624,542
10 transactions · 8 stateful · 2026-06-30 06:16:15 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,624,542 · 10 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1c4bca4b…8cd9
0xd32edf…ff58
3 touches
1 conflict
0x3a6769be…0387
0x065c9d…c394
2 touches
0 conflicts
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0x65cbf0b4…a230
0x065c9d…c394
2 touches
0 conflicts
0x6c40f282…f8f3
0x065c9d…c394
2 touches
0 conflicts
0x788663de…e099
0x065c9d…c394
2 touches
0 conflicts
0x8412e53d…566a
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