← previous blocknext block →recent activity
Analyzing
Block #82,019,309
14 transactions · 8 stateful · 2026-06-18 04:28:44 UTC
Parallelism
86/100
Blocked
13%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,019,309 · 14 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
0x7042fb40…145c
0x065c9d…c394
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x57823ae3…e4f5
0x065c9d…c394
3 touches
1 conflict
0xc4820e61…55b3
0x065c9d…c394
3 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x68faa0b9…14af
0x98dc6e…8633
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 0x7042fb4052…9d145c
Audit this contract →
← previous block·next block →recent activity