pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,546,721
← previous block
next block →
recent activity
Analyzing
Block #92,546,721
10 transactions · 10 stateful · 2026-08-02 17:20:32 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,546,721
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
executeBatch
#3
execFwdPositionOps
· blocks 1
#4
setData
#5
0x3f5c179b
#7
batchUpdate
#8
updateDataFeedsValuesPartial
#9
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x534ef679…ae9d
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x207c903e…9e16
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x17bbe4f8…08c5
0xe52b14…7230
2 touches
0 conflicts
0x32363a87…c2cc
0xe52b14…7230
2 touches
0 conflicts
0x32363a87…c2ce
0xe52b14…7230
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
0x534ef679c5…43ae9d
Audit this contract →
← previous block
·
next block →
recent activity