← previous blocknext block →recent activity
Analyzing
Block #84,615,868
11 transactions · 10 stateful · 2026-06-30 05:18:37 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,615,868 · 11 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
1w04w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0x159b8597…48a4
0x34b655…2a6f
3 touches
1 conflict
0x6356f093…48bd
0x065c9d…c394
2 touches
0 conflicts
0x8168293c…c638
0x065c9d…c394
2 touches
0 conflicts
0x961d1776…d532
0x065c9d…c394
2 touches
0 conflicts
0x9851a0b3…1ce6
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