← previous blocknext block →recent activity
Analyzing
Block #86,753,511
21 transactions · 18 stateful · 2026-07-10 03:00:19 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,753,511 · 21 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
1w02w14w25w38w09w110w211w314w015w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26f43a0e…7ccb
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
8 touches
6 conflicts
0x99d9963b…7080
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xb538c6fa…9ae6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x410b84ab…1dbc
0x34b655…2a6f
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
6 conflicts on slot 0x26f43a0e39…a77ccb
Audit this contract →
← previous block·next block →recent activity