pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,307,400
← previous block
next block →
recent activity
Analyzing
Block #94,307,400
7 transactions · 5 stateful · 2026-08-08 21:05:19 UTC
Parallelism
57
/100
Blocked
40
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,307,400
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x009e5079…077f
0x34b655…2a6f
2 touches
0 conflicts
0x00e2c296…0001
0x34b655…2a6f
2 touches
0 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
2 touches
0 conflicts
0x0cab9ea4…924f
0x34b655…2a6f
2 touches
0 conflicts
0x147c952c…b00d
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity