← previous blocknext block →recent activity
Analyzing
Block #82,705,013
38 transactions · 25 stateful · 2026-06-21 08:46:28 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,705,013 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w410w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2174407d…dfbf
0x065c9d…c394
3 touches
1 conflict
0x47087ffd…d1ff
0x065c9d…c394
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity