← previous blocknext block →recent activity
Analyzing
Block #86,167,639
22 transactions · 21 stateful · 2026-07-07 09:43:35 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,167,639 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w07w110w111w012w115w216w317w319w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc3e33dec…f9f3
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd0de09d7…1d6b
0x065c9d…c394
5 touches
3 conflicts
0x7b0297c7…8f17
0x34b655…2a6f
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
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
6 conflicts on slot 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity