← previous blocknext block →recent activity
Analyzing
Block #81,629,485
18 transactions · 15 stateful · 2026-06-16 09:08:54 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,629,485 · 18 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
1w02w14w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x03367510…9b91
0x065c9d…c394
4 touches
1 conflict
0x1f762e4a…058c
0x065c9d…c394
4 touches
1 conflict
0x7a076ccc…f57a
0x065c9d…c394
4 touches
1 conflict
0x8901be9c…e385
0x065c9d…c394
4 touches
1 conflict
0x8f5f2b03…4a76
0x065c9d…c394
4 touches
1 conflict
0xd2321f19…069e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity