pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,947,879
← previous block
next block →
recent activity
Analyzing
Block #98,947,879
9 transactions · 9 stateful · 2026-08-25 04:24:23 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,947,879
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 2
#4
0x3f5c179b
#7
0x6a8d196f
#8
setData
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b53436c…2ec3
0x34b655…2a6f
4 touches
1 conflict
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0xc406fe27…9ab2
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
2 touches
0 conflicts
0x20c6f08f…36e5
0x34b655…2a6f
2 touches
0 conflicts
0x304d2f3c…172c
0x34b655…2a6f
2 touches
0 conflicts
0x4387ba94…e195
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0x3b53436c6f…c62ec3
Audit this contract →
← previous block
·
next block →
recent activity