← previous blocknext block →recent activity
Analyzing
Block #81,478,159
7 transactions · 7 stateful · 2026-06-15 16:20:55 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,478,159 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x5e64532e…ec9a
0x065c9d…c394
4 touches
1 conflict
0x6d497c01…0e07
0x065c9d…c394
3 touches
1 conflict
0x9ebef740…0fa6
0x065c9d…c394
2 touches
0 conflicts
0xad66d537…ca67
0x065c9d…c394
2 touches
0 conflicts
0xc7948497…596d
0x065c9d…c394
2 touches
0 conflicts
0xc8f5845d…cf0e
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity