pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,929,764
← previous block
next block →
recent activity
Analyzing
Block #86,929,764
8 transactions · 7 stateful · 2026-07-10 22:38:18 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,929,764
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#6
0x6a5174d2
#7
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fa1ba4f…a56f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7f2141d6…42bd
0x34b655…2a6f
4 touches
1 conflict
0x8fa1ba4f…a570
0x34b655…2a6f
4 touches
1 conflict
0x96c303ae…c7ef
0x34b655…2a6f
4 touches
1 conflict
0xa4d8ef05…8ea2
0x34b655…2a6f
3 touches
1 conflict
0x993a8fb9…e504
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
0x8fa1ba4f68…24a56f
Audit this contract →
← previous block
·
next block →
recent activity