← previous blocknext block →recent activity
Analyzing
Block #82,754,753
15 transactions · 11 stateful · 2026-06-21 14:18:33 UTC
Parallelism
80/100
Blocked
18%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,754,753 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x4ed7ca85…8164
0x065c9d…c394
2 touches
0 conflicts
0xc443c95f…2f9a
0x065c9d…c394
2 touches
0 conflicts
0x451f0c72…64f0
0x57ea24…2cec
2 touches
0 conflicts
0x80b93925…6c8e
0x57ea24…2cec
2 touches
0 conflicts
0x06e40499…165e
0x69df8a…6292
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity