← previous blocknext block →recent activity
Analyzing
Block #86,991,525
33 transactions · 31 stateful · 2026-07-11 05:31:00 UTC
Parallelism
85/100
Blocked
52%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,991,525 · 33 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
1w02w13w14w15w26w28w29w311w313w014w115w216w319w020w121w223w025w128w430w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0002
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xd0ec60a1…d246
0x1b6862…e19c
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