← previous blocknext block →recent activity
Analyzing
Block #86,220,861
31 transactions · 25 stateful · 2026-07-07 15:38:59 UTC
Parallelism
90/100
Blocked
28%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,220,861 · 31 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w19w111w012w114w023w224w125w226w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0223e2e8…9862
0x34b655…2a6f
4 touches
1 conflict
0x181732de…9796
0x34b655…2a6f
4 touches
1 conflict
0x399f2673…b3a7
0x34b655…2a6f
4 touches
1 conflict
0x4843c99d…44b1
0x34b655…2a6f
4 touches
1 conflict
0x584cbe31…38e5
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity