pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,021,226
← previous block
next block →
recent activity
Analyzing
Block #84,021,226
10 transactions · 8 stateful · 2026-06-27 11:15:35 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,021,226
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a3fb14f
#2
execFwdPositionOps
· blocks 1
#3
0x0c7abd22
#4
closeTrade
#5
execFwdPositionOps
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93d680fb…ac21
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0d1ec7b7…e2a8
0x34b655…2a6f
2 touches
0 conflicts
0x19007011…d3df
0x34b655…2a6f
2 touches
0 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x49037046…6742
0x34b655…2a6f
2 touches
0 conflicts
0x4b29cd54…124d
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
1 conflict on slot
0x93d680fb3b…fdac21
Audit this contract →
← previous block
·
next block →
recent activity