← previous blocknext block →recent activity
Analyzing
Block #81,030,617
14 transactions · 11 stateful · 2026-06-13 14:40:07 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,030,617 · 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
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfb64e9ec…34fd
0x2a68ba…90c5
2 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x40faf0d5…5372
0x065c9d…c394
2 touches
0 conflicts
0x4a73ead2…2676
0x065c9d…c394
2 touches
0 conflicts
0x2cf513b0…067b
0x34b655…2a6f
2 touches
0 conflicts
0x40579056…c419
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
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