← previous blocknext block →recent activity
Analyzing
Block #82,524,865
12 transactions · 10 stateful · 2026-06-20 12:40:47 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,524,865 · 12 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ec8314e…0e89
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x0d850362…dd27
0x065c9d…c394
3 touches
1 conflict
0xee7501d2…c404
0x065c9d…c394
3 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
2 touches
0 conflicts
0x320a4123…4d39
0x34b655…2a6f
2 touches
0 conflicts
0x71cc73a0…d523
0x34b655…2a6f
2 touches
0 conflicts
0x86cea35b…bdff
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 0x5ec8314ee8…df0e89
Audit this contract →
← previous block·next block →recent activity