← previous blocknext block →recent activity
Analyzing
Block #86,232,473
23 transactions · 19 stateful · 2026-07-07 16:56:30 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,232,473 · 23 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
1w02w13w24w37w110w111w012w116w219w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf7be3403…2c0b
0xd32edf…ff58
7 touches
6 conflicts
0x01076862…1db7
0x34b655…2a6f
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x9c73c55d…2db4
0x40c49f…2af0
4 touches
1 conflict
0xb41e4bb8…86e3
0x40c49f…2af0
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity