pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,448,150
← previous block
next block →
recent activity
Analyzing
Block #92,448,150
9 transactions · 8 stateful · 2026-08-02 09:04:45 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,448,150
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x3f5c179b
· blocks 1
#3
execFwdPositionOps
· blocks 1
#5
execOrders
#7
setData
#8
0x59558d29
#2
batchUpdate
#4
execFwdPositionOps
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd77a43ef…c635
0x40c49f…2af0
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xbc8d2ca3…f2c1
0x34b655…2a6f
4 touches
1 conflict
0xc4c97890…c849
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
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:
0x40c49f17…d22af0
1 conflict on slot
0xd77a43efea…22c635
Audit this contract →
← previous block
·
next block →
recent activity