← previous blocknext block →recent activity
Analyzing
Block #86,272,217
12 transactions · 11 stateful · 2026-07-07 21:21:53 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,272,217 · 12 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
1w04w16w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0014
0x2f55a2…8375
4 touches
1 conflict
0x0365c9a6…9294
0x000000…8ba3
2 touches
0 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
2 touches
0 conflicts
0x600ecc7e…dd94
0x065c9d…c394
2 touches
0 conflicts
0xbb1f5a41…7fb4
0x065c9d…c394
2 touches
0 conflicts
0xbb4a675f…1cf2
0x065c9d…c394
2 touches
0 conflicts
0xbf469821…454c
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity