pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,490,652
← previous block
next block →
recent activity
Analyzing
Block #98,490,652
20 transactions · 16 stateful · 2026-08-23 13:27:52 UTC
Parallelism
90
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,490,652
· 20 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
matchOrders
#3
0xa96df62f
#4
0x59558d29
#5
execPerpOps
#6
execPerpOps
#7
execPerpOps
· blocks 1
#10
updateDataFeedsValuesPartial
#11
execFwdPositionOpsV2
· blocks 1
#13
0x3f5c179b
#14
0x3f5c179b
#15
setData
#17
execOrders
#18
execOrders
#19
execOrders
#8
execPerpOps
#9
0x5acec890
#12
execFwdPositionOpsV2
#16
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w0
8
w1
9
w1
11
w0
12
w1
16
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd4ef1f4f…cffb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
2 touches
0 conflicts
0xd5b10148…e635
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
0x51fc8795c8…571266
Audit this contract →
← previous block
·
next block →
recent activity