← previous blocknext block →recent activity
Analyzing
Block #86,851,741
23 transactions · 18 stateful · 2026-07-10 13:56:39 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,851,741 · 23 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
1w02w03w17w08w09w111w120w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3413a430…234a
0x34b655…2a6f
6 touches
3 conflicts
0xf81d0d0f…cf78
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0e525f1d…dfed
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x505d32fe…14ad
0x34b655…2a6f
4 touches
1 conflict
0xa86351b8…2c5a
0x34b655…2a6f
4 touches
1 conflict
0xa8667a2e…b5e2
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: Perpl
3 conflicts on slot 0x3413a43072…a1234a
Audit this contract →
← previous block·next block →recent activity