← previous blocknext block →recent activity
Analyzing
Block #86,246,299
37 transactions · 27 stateful · 2026-07-07 18:28:53 UTC
Parallelism
70/100
Blocked
63%
Avg conflicts / tx
1.32
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,246,299 · 37 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
1w02w14w05w17w29w010w113w314w215w016w017w318w119w220w324w425w528w729w831w932w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xdb0d6a04…ab4e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
8 touches
6 conflicts
0x415e59be…3f62
0xd32edf…ff58
7 touches
6 conflicts
0x9a2cd1ed…9eba
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity