← previous blocknext block →recent activity
Analyzing
Block #86,797,514
16 transactions · 14 stateful · 2026-07-10 07:54:03 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
1.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,797,514 · 16 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
3w04w15w26w37w48w59w615w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b9f02c4…6fec
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x06c980ab…5577
0x34b655…2a6f
6 touches
3 conflicts
0x263aa68b…6c6a
0x34b655…2a6f
4 touches
1 conflict
0x7b9d95d5…5d76
0x34b655…2a6f
4 touches
1 conflict
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 0x0b9f02c40e…8f6fec
Audit this contract →
← previous block·next block →recent activity