← previous blocknext block →recent activity
Analyzing
Block #86,664,232
24 transactions · 22 stateful · 2026-07-09 17:04:04 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,664,232 · 24 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
3w04w15w16w27w08w19w210w011w112w213w314w015w118w422w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x9459cf47…a8a3
0x065c9d…c394
8 touches
6 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 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