← previous blocknext block →recent activity
Analyzing
Block #86,681,089
13 transactions · 10 stateful · 2026-07-09 18:56:36 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,681,089 · 13 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
1w02w13w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa58f1d73…9ce0
0x34b655…2a6f
6 touches
3 conflicts
0x68ae6fca…0224
0x34b655…2a6f
6 touches
3 conflicts
0xa58f1d73…9ce1
0x34b655…2a6f
6 touches
3 conflicts
0xf25d02ec…c327
0x34b655…2a6f
4 touches
1 conflict
0x09b6d501…a338
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity