pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,471,075
← previous block
next block →
recent activity
Analyzing
Block #94,471,075
7 transactions · 6 stateful · 2026-08-09 10:57:04 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,471,075
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postPriceList
#2
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a785d78
#6
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xa88a59cd…35ac
0x34b655…2a6f
4 touches
1 conflict
0x06e6ff87…e712
0x34b655…2a6f
2 touches
0 conflicts
0x07d94be1…7fa8
0x34b655…2a6f
2 touches
0 conflicts
0x09bde27f…671c
0x34b655…2a6f
2 touches
0 conflicts
0x3bc2b823…6d96
0x34b655…2a6f
2 touches
0 conflicts
0x3df0422c…fd38
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity