pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,460,767
← previous block
next block →
recent activity
Analyzing
Block #98,460,767
12 transactions · 11 stateful · 2026-08-23 10:57:26 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,460,767
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x32d01e04
#3
0x59558d29
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
· blocks 1
#7
0xed82b078
#8
approve
#9
0x6a8ad28e
#10
setData
#11
execOrders
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24ffe208…a273
0x34b655…2a6f
4 touches
1 conflict
0x832cf0ec…3457
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x2cf00801…51b8
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x484bc84e…40da
0x34b655…2a6f
2 touches
0 conflicts
0x514fa990…f462
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
0x24ffe20885…f0a273
Audit this contract →
← previous block
·
next block →
recent activity