pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,280,797
← previous block
next block →
recent activity
Analyzing
Block #91,280,797
10 transactions · 8 stateful · 2026-07-29 07:11:24 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
#91,280,797
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#5
execOrders
#6
execFwdPositionOps
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a606d8a…9700
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd4
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd5
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x089aecdd…92ac
0x34b655…2a6f
2 touches
0 conflicts
0x0c36b86e…3ea8
0x34b655…2a6f
2 touches
0 conflicts
0x212003dc…a249
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
0x7a606d8a84…489700
Audit this contract →
← previous block
·
next block →
recent activity