pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,606,039
← previous block
next block →
recent activity
Analyzing
Block #84,606,039
9 transactions · 7 stateful · 2026-06-30 04:13:11 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,606,039
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
forward
#6
execFwdPositionOps
· blocks 1
#8
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c9541ce…9135
0x34b655…2a6f
4 touches
1 conflict
0x32359294…7113
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xb45d4c57…a219
0x34b655…2a6f
4 touches
1 conflict
0x59f816ee…c658
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000d
0xef3c6c…ceb2
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
0x6c9541cec2…b19135
Audit this contract →
← previous block
·
next block →
recent activity