pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,331,785
← previous block
next block →
recent activity
Analyzing
Block #84,331,785
11 transactions · 10 stateful · 2026-06-28 21:44:13 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,331,785
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
0x6a419625
#5
setData
#6
execOrders
· blocks 2
#9
0xc7e3ec2c
#10
0xc7e3ec2c
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2f7781d6…e632
0x34b655…2a6f
4 touches
1 conflict
0x98e95e72…24dd
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xece967b0…8069
0x34b655…2a6f
4 touches
1 conflict
0x3977c7aa…6fa3
0x34b655…2a6f
2 touches
0 conflicts
0x41dc8e20…cb2d
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity