← previous blocknext block →recent activity
Analyzing
Block #82,655,183
20 transactions · 13 stateful · 2026-06-21 03:13:18 UTC
Parallelism
90/100
Blocked
31%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,655,183 · 20 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
2w03w07w110w011w117w018w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0dc66…111b
0x065c9d…c394
4 touches
1 conflict
0x0ede2450…40fd
0x5afd3e…7620
4 touches
1 conflict
0x310650a5…2741
0x5afd3e…7620
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x8a7af3fd…72a7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x91b0dc66a8…c5111b
Audit this contract →
← previous block·next block →recent activity