pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,285,952
← previous block
next block →
recent activity
Analyzing
Block #98,285,952
11 transactions · 10 stateful · 2026-08-22 20:17:37 UTC
Parallelism
82
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,285,952
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
setData
#3
execOrders
#4
0x59558d29
#5
0x5acec890
· blocks 2
#8
0xed82b078
#9
execOrders
#6
0x928e4afa
#7
execFwdPositionOpsV2
#10
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dedaff6…161b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x4e135144…4167
0x34b655…2a6f
2 touches
0 conflicts
0x54907f2c…4a40
0x34b655…2a6f
2 touches
0 conflicts
0x549c2377…ad00
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
0x6dedaff684…2d161b
Audit this contract →
← previous block
·
next block →
recent activity