pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,445,137
← previous block
next block →
recent activity
Analyzing
Block #98,445,137
11 transactions · 10 stateful · 2026-08-23 09:38:31 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,445,137
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
· blocks 1
#4
execOrder
· blocks 1
#5
0x59558d29
#6
0x29eed2d3
#8
0xed82b078
#9
setData
#10
execOrders
#3
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf148676d…14d7
0x34b655…2a6f
4 touches
1 conflict
0x10b629c1…3ca7
0x34b655…2a6f
2 touches
0 conflicts
0x1c86941a…9e27
0x34b655…2a6f
2 touches
0 conflicts
0x27d3333e…7d38
0x34b655…2a6f
2 touches
0 conflicts
0x47679846…4d1b
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
0xd66696e0dc…230842
Audit this contract →
← previous block
·
next block →
recent activity