pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,789,189
← previous block
next block →
recent activity
Analyzing
Block #86,789,189
11 transactions · 7 stateful · 2026-07-10 06:58:28 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,789,189
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#5
executeBatch
#7
0x0f6795d9
#8
setData
#9
0x4ec09e…b103
#10
withdraw
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0edff147…13ee
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x977e7afc…bf14
0x34b655…2a6f
4 touches
1 conflict
0x0edff147…13ed
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa243ce39…3ff4
0x34b655…2a6f
2 touches
0 conflicts
0xcc9b0abb…633c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x0edff14741…4713ee
Audit this contract →
← previous block
·
next block →
recent activity