← previous blocknext block →recent activity
Analyzing
Block #81,102,205
17 transactions · 13 stateful · 2026-06-13 22:37:33 UTC
Parallelism
76/100
Blocked
23%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,102,205 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb519d01c…8445
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xb54577a9…86dc
0xd32edf…ff58
3 touches
1 conflict
0x8fb5f99f…e7f7
0x065c9d…c394
2 touches
0 conflicts
0x9fef97b4…2729
0x065c9d…c394
2 touches
0 conflicts
0xe2cc89ec…4444
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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