pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,382,661
← previous block
next block →
recent activity
Analyzing
Block #98,382,661
9 transactions · 7 stateful · 2026-08-23 04:24:12 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,382,661
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
0x928e4afa
#4
execFwdPositionOpsV2
· blocks 1
#6
setData
#7
execOrders
#8
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xf4c813a8…1a2e
0x34b655…2a6f
4 touches
1 conflict
0x00ff732e…49a6
0x34b655…2a6f
2 touches
0 conflicts
0x08782b3c…5856
0x34b655…2a6f
2 touches
0 conflicts
0x33a0620a…8b9e
0x34b655…2a6f
2 touches
0 conflicts
0x40f8bf08…aa48
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
0x1a2055c785…e29054
Audit this contract →
← previous block
·
next block →
recent activity