pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,561,293
← previous block
next block →
recent activity
Analyzing
Block #98,561,293
11 transactions · 11 stateful · 2026-08-23 19:34:57 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,561,293
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrders
#3
0x59558d29
#4
0x5acec890
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#8
commit
#9
setData
#10
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1408e7c7…f324
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x16722673…9c38
0x34b655…2a6f
2 touches
0 conflicts
0x177ae142…a901
0x34b655…2a6f
2 touches
0 conflicts
0x1fc96968…a760
0x34b655…2a6f
2 touches
0 conflicts
0x3093e806…bde2
0x34b655…2a6f
2 touches
0 conflicts
0x3ae7cc07…6f6e
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
0x1408e7c773…87f324
Audit this contract →
← previous block
·
next block →
recent activity