← previous blocknext block →recent activity
Analyzing
Block #81,201,958
18 transactions · 14 stateful · 2026-06-14 09:41:31 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,201,958 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x63c34aa0…fcc8
0x065c9d…c394
4 touches
1 conflict
0x8a54b39b…2dbd
0x065c9d…c394
3 touches
1 conflict
0xe12eb945…4eb7
0x065c9d…c394
3 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0x08de772c…8e84
0x2a68ba…90c5
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity