pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,321,588
← previous block
next block →
recent activity
Analyzing
Block #98,321,588
11 transactions · 10 stateful · 2026-08-22 23:16:58 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,321,588
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x7b84f330
#3
execOrders
#4
0x59558d29
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
#9
setData
#10
forwardERC20
#5
0x928e4afa
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0xed3b0943…f01b
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5b
0x34b655…2a6f
4 touches
1 conflict
0x05286dbb…4517
0x34b655…2a6f
4 touches
1 conflict
0x10a5a231…be40
0x34b655…2a6f
4 touches
1 conflict
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
0xf4db760d0a…f0fc5c
Audit this contract →
← previous block
·
next block →
recent activity