← previous blocknext block →recent activity
Analyzing
Block #86,222,049
55 transactions · 39 stateful · 2026-07-07 15:46:53 UTC
Parallelism
80/100
Blocked
64%
Avg conflicts / tx
1.2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,222,049 · 55 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w613w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xfb42c6d2…cb0c
0xd32edf…ff58
13 touches
21 conflicts
0x1ccfa324…0b93
0x0a917f…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0x0a917f…7777
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 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