pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,006,000
← previous block
next block →
recent activity
Analyzing
Block #92,006,000
13 transactions · 12 stateful · 2026-07-31 20:01:06 UTC
Parallelism
85
/100
Blocked
25
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,006,000
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
postStateList
#3
0x0c7abd22
#4
updateDataFeedsValuesPartial
#5
0x6a6cff7a
#6
setData
· blocks 1
#8
execOrders
· blocks 1
#10
0x59558d29
· blocks 1
#12
0xc7e3ec2c
#7
setData
#9
execOrders
#11
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w0
9
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0x06ad1460…695f
0x34b655…2a6f
4 touches
1 conflict
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x19bbf80f…0615
0x34b655…2a6f
4 touches
1 conflict
0x2979e2dd…335e
0x34b655…2a6f
4 touches
1 conflict
0x514ced63…4b06
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity