← previous blocknext block →recent activity
Analyzing
Block #86,634,273
22 transactions · 18 stateful · 2026-07-09 13:42:42 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,634,273 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w510w012w013w114w120w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5eb
0x34b655…2a6f
12 touches
15 conflicts
0x3151b440…d0aa
0x34b655…2a6f
12 touches
15 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
12 touches
15 conflicts
0x77cf3c7b…a722
0x34b655…2a6f
12 touches
15 conflicts
0xac6f24e7…c98b
0x34b655…2a6f
12 touches
15 conflicts
0xdb86d50f…b5fc
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5ea
0x34b655…2a6f
12 touches
15 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity