pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,080,619
← previous block
next block →
recent activity
Analyzing
Block #98,080,619
8 transactions · 8 stateful · 2026-08-22 03:03:53 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,080,619
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x59558d29
#4
execFwdPositionOpsV2
· blocks 2
#5
forward
#6
execFwdPositionOpsV2
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x517a6935…e298
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xe3ab4180…f888
0x34b655…2a6f
3 touches
1 conflict
0xf7c6e847…5468
0x34b655…2a6f
3 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
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
0x261cbea79d…12e35d
Audit this contract →
← previous block
·
next block →
recent activity