← previous blocknext block →recent activity
Analyzing
Block #81,634,088
18 transactions · 13 stateful · 2026-06-16 09:39:31 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,634,088 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w410w516w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7baa4daf…189e
0x065c9d…c394
4 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
3 touches
1 conflict
0x72c47f00…9bf8
0x065c9d…c394
3 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0xaf7c4e2f…2922
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity