pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,458,792
← previous block
next block →
recent activity
Analyzing
Block #98,458,792
12 transactions · 11 stateful · 2026-08-23 10:47: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,458,792
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0xab083028
#3
execOrders
#4
0x59558d29
#5
execPerpOps
#6
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
#9
executeBatch
#10
0x3f5c179b
#11
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xcaa5e459…c7eb
0x34b655…2a6f
4 touches
1 conflict
0xe1ac7bbd…88ad
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x051f132a…6917
0x34b655…2a6f
2 touches
0 conflicts
0x051f132a…6918
0x34b655…2a6f
2 touches
0 conflicts
0x12e7c471…901c
0x34b655…2a6f
2 touches
0 conflicts
0x1e7b8aac…1778
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
0x737acb7813…fafce8
Audit this contract →
← previous block
·
next block →
recent activity