← previous blocknext block →recent activity
Analyzing
Block #81,006,544
14 transactions · 13 stateful · 2026-06-13 11:59:45 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,006,544 · 14 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
1w02w13w24w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x5f5af5e6…d5ae
0x065c9d…c394
2 touches
0 conflicts
0x7878e773…bad1
0x065c9d…c394
2 touches
0 conflicts
0xa2c53984…9e74
0x065c9d…c394
2 touches
0 conflicts
0xd05fc67f…4d87
0x065c9d…c394
2 touches
0 conflicts
0xf01748bc…d5a2
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity