pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,163,468
← previous block
next block →
recent activity
Analyzing
Block #92,163,468
10 transactions · 10 stateful · 2026-08-01 09:13:05 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,163,468
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
· blocks 1
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
claim
#7
execOrders
#8
setData
#9
0x59558d29
#3
0x5acec890
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
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0x31118d31…c786
0x34b655…2a6f
2 touches
0 conflicts
0x3280f198…a541
0x34b655…2a6f
2 touches
0 conflicts
0x35b0198e…3e0d
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
0x34d95d945c…603a16
Audit this contract →
← previous block
·
next block →
recent activity