pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,604,875
← previous block
next block →
recent activity
Analyzing
Block #84,604,875
11 transactions · 10 stateful · 2026-06-30 04:05:25 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,604,875
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
execOrders
· blocks 2
#5
execFwdPositionOps
#6
updatePosition
#7
execFwdPositionOps
#8
setData
#9
execOrders
· blocks 1
#4
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
9
w0
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4384dd01…4f99
0x34b655…2a6f
6 touches
3 conflicts
0x40b5f387…a164
0x34b655…2a6f
6 touches
3 conflicts
0x343db577…2962
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x24227bc5…cb16
0x34b655…2a6f
4 touches
1 conflict
0xd58b9a66…1c23
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc905946…e548
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
3 conflicts on slot
0x4384dd01db…564f99
Audit this contract →
← previous block
·
next block →
recent activity