pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,766,203
← previous block
next block →
recent activity
Analyzing
Block #86,766,203
12 transactions · 8 stateful · 2026-07-10 04:25:02 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,766,203
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
execPerpOps
#4
execPerpOps
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
0xd10227eb
#10
updateDataFeedsValuesPartial
#11
setData
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x58693d48…0f7c
0x34b655…2a6f
4 touches
1 conflict
0x6122676a…1970
0x34b655…2a6f
4 touches
1 conflict
0x6122676a…1971
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x7d6e48e8…f2b5
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity