← previous blocknext block →recent activity
Analyzing
Block #86,773,431
16 transactions · 14 stateful · 2026-07-10 05:13:21 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,773,431 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w111w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x567bb003…113a
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
10 touches
10 conflicts
0x278d3ffb…20ba
0x34b655…2a6f
10 touches
10 conflicts
0x2e30095c…a92d
0x34b655…2a6f
10 touches
10 conflicts
0x3d4584df…ffed
0x34b655…2a6f
10 touches
10 conflicts
0x462dc823…ab0b
0x34b655…2a6f
10 touches
10 conflicts
0x4a02df79…3e0b
0x34b655…2a6f
10 touches
10 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: Perpl
15 conflicts on slot 0x567bb0034c…9f113a
Audit this contract →
← previous block·next block →recent activity