pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,561,949
← previous block
next block →
recent activity
Analyzing
Block #98,561,949
15 transactions · 13 stateful · 2026-08-23 19:38:20 UTC
Parallelism
87
/100
Blocked
15
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,561,949
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
· blocks 1
#3
0x0c7abd22
#4
0x59558d29
#5
execPerpOps
#6
execPerpOps
#8
execFwdPositionOpsV2
#9
0x3f5c179b
#10
execFwdPositionOpsV2
#11
transfer
· blocks 1
#13
setData
#14
execOrders
#7
0x928e4afa
#12
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4b350eb…8c96
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x4ba944db…a451
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
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
0xb4b350ebf7…dc8c96
Audit this contract →
← previous block
·
next block →
recent activity