pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,148,936
← previous block
next block →
recent activity
Analyzing
Block #98,148,936
13 transactions · 12 stateful · 2026-08-22 08:48:20 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,148,936
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0xa96df62f
#3
matchOrders
#4
0x59558d29
#5
execPerpOps
#6
execPerpOps
#7
execFwdPositionOpsV2
· blocks 1
#8
0x3f5c179b
#9
execOrders
#10
setData
#11
execOrders
#12
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w0
11
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa75029c…d62c
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x84f59b53…daaa
0x34b655…2a6f
2 touches
0 conflicts
0xac808a27…82db
0x34b655…2a6f
2 touches
0 conflicts
0xccebf5c5…8758
0x34b655…2a6f
2 touches
0 conflicts
0xccebf5c5…8759
0x34b655…2a6f
2 touches
0 conflicts
0xe1c4e5ce…0de3
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
0xfa75029c19…e9d62c
Audit this contract →
← previous block
·
next block →
recent activity