← previous blocknext block →recent activity
Analyzing
Block #86,775,226
24 transactions · 21 stateful · 2026-07-10 05:25:19 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,775,226 · 24 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
1w02w14w08w19w211w313w114w216w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x283c0899…c778
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0xdc2df17e…6e2b
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x10970e1d…90df
0x34b655…2a6f
4 touches
1 conflict
0x119694b6…b8dc
0x34b655…2a6f
4 touches
1 conflict
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 0x283c089903…e4c778
Audit this contract →
← previous block·next block →recent activity