pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,534,704
← previous block
next block →
recent activity
Analyzing
Block #92,534,704
9 transactions · 8 stateful · 2026-08-02 16:20:06 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,534,704
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 2
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#6
0x6a6f6eae
#7
setData
#8
execOrders
#2
0x5acec890
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05495d91…11b0
0x34b655…2a6f
2 touches
0 conflicts
0x3a22223a…b7dd
0x34b655…2a6f
2 touches
0 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
2 touches
0 conflicts
0x4402c2ee…a884
0x34b655…2a6f
2 touches
0 conflicts
0x491015fd…37a0
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
0xff19684070…f2a453
Audit this contract →
← previous block
·
next block →
recent activity