← previous blocknext block →recent activity
Analyzing
Block #82,018,621
16 transactions · 9 stateful · 2026-06-18 04:24:09 UTC
Parallelism
88/100
Blocked
11%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,018,621 · 16 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91eba5ff…3997
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0xde9bb5ee…6da8
0x065c9d…c394
3 touches
1 conflict
0x0e20ead2…e08e
0x065c9d…c394
3 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x26abe30c…f680
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
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 0x91eba5ff52…803997
Audit this contract →
← previous block·next block →recent activity