← previous blocknext block →recent activity
Analyzing
Block #81,479,015
14 transactions · 14 stateful · 2026-06-15 16:26:39 UTC
Parallelism
79/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,479,015 · 14 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd3898748…5e05
0x065c9d…c394
3 touches
1 conflict
0x8d3400e4…7c84
0x065c9d…c394
3 touches
1 conflict
0x9809bd6d…e682
0x065c9d…c394
2 touches
0 conflicts
0xa8da8728…2317
0x065c9d…c394
2 touches
0 conflicts
0xc6f8c519…6236
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x69df8a…6292
2 touches
0 conflicts
0x45f562b2…9294
0x69df8a…6292
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