← previous blocknext block →recent activity
Analyzing
Block #82,049,089
15 transactions · 15 stateful · 2026-06-18 07:47:11 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,049,089 · 15 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
1w03w14w05w19w010w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x1bbc01d7…0bcb
0x34b655…2a6f
4 touches
1 conflict
0x21e43e72…d2f6
0x34b655…2a6f
4 touches
1 conflict
0x25aa9d32…d4df
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x26abe30c…f680
0x34b655…2a6f
4 touches
1 conflict
0x32595425…ba05
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity