← previous blocknext block →recent activity
Analyzing
Block #82,269,938
13 transactions · 12 stateful · 2026-06-19 08:20:16 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,269,938 · 13 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57966662…fc57
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x8ce653d0…6ac7
0x065c9d…c394
3 touches
1 conflict
0xd1383e66…383e
0x065c9d…c394
3 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
2 touches
0 conflicts
0x42deaa13…f045
0x34b655…2a6f
2 touches
0 conflicts
0x4786839b…c29a
0x34b655…2a6f
2 touches
0 conflicts
0x8cf58d5b…f3e4
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 0x5796666240…9afc57
Audit this contract →
← previous block·next block →recent activity