← previous blocknext block →recent activity
Analyzing
Block #81,407,231
14 transactions · 14 stateful · 2026-06-15 08:28:19 UTC
Parallelism
64/100
Blocked
29%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,407,231 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x12c68b7c…a221
0x065c9d…c394
2 touches
0 conflicts
0x1f0f4ea8…b66e
0x065c9d…c394
2 touches
0 conflicts
0x37c80416…518c
0x065c9d…c394
2 touches
0 conflicts
0xcf2157cb…736b
0x065c9d…c394
2 touches
0 conflicts
0xf6d34cc6…0ced
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity