← previous blocknext block →recent activity
Analyzing
Block #81,102,149
24 transactions · 15 stateful · 2026-06-13 22:37:11 UTC
Parallelism
92/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,102,149 · 24 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
5w06w17w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1381b7e2…372f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa0908a31…5a88
0x065c9d…c394
3 touches
1 conflict
0x0ea12472…1c7a
0x065c9d…c394
3 touches
1 conflict
0x8d79c2b5…437c
0x065c9d…c394
2 touches
0 conflicts
0xc3c8642a…7da5
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
1 conflict on slot 0x1381b7e26a…a0372f
Audit this contract →
← previous block·next block →recent activity