pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,604,949
← previous block
next block →
recent activity
Analyzing
Block #84,604,949
13 transactions · 11 stateful · 2026-06-30 04:05:55 UTC
Parallelism
85
/100
Blocked
27
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,604,949
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
setData
#5
execute
#6
execOrders
· blocks 2
#7
execFwdPositionOps
· blocks 1
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#8
execFwdPositionOps
#11
execOrders
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w0
8
w1
11
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa16b3e4e…0787
0x34b655…2a6f
4 touches
1 conflict
0xb44d5376…33cc
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0x0db8a3ed…1b02
0x1001ff…1001
2 touches
0 conflicts
0xc6f1b3af…c97c
0x1001ff…1001
2 touches
0 conflicts
0x00000000…0000
0x276664…5732
2 touches
0 conflicts
0x00000000…0002
0x276664…5732
2 touches
0 conflicts
0x00000000…0004
0x276664…5732
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
0xa16b3e4e62…240787
Audit this contract →
← previous block
·
next block →
recent activity