← previous blocknext block →recent activity
Analyzing
Block #81,832,087
25 transactions · 21 stateful · 2026-06-17 07:38:49 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,832,087 · 25 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
1w02w04w15w26w19w010w111w213w015w018w220w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0xdec5bfea…d17f
0xa6afd3…d132
6 touches
3 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
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
3 conflicts on slot 0x160f117d43…518e90
Audit this contract →
← previous block·next block →recent activity