← previous blocknext block →recent activity
Analyzing
Block #82,335,376
10 transactions · 9 stateful · 2026-06-19 15:36:39 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,335,376 · 10 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
4w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeea136c9…156b
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda86e594…d0f2
0x065c9d…c394
3 touches
1 conflict
0x2de924a0…daf5
0x065c9d…c394
3 touches
1 conflict
0x5311f864…0984
0x754704…b603
2 touches
0 conflicts
0xfa68a9ee…dba7
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
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 0xeea136c9e7…08156b
Audit this contract →
← previous block·next block →recent activity