pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,480,096
← previous block
next block →
recent activity
Analyzing
Block #97,480,096
10 transactions · 7 stateful · 2026-08-20 00:15:02 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,480,096
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
· blocks 1
#2
0x41a8f47c
#3
setData
#5
execOrder
· blocks 1
#6
placeAndExecuteMarketSell
#7
placeAndExecuteMarketSell
#9
execOrders
#4
0xab083028
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdae0fba1…c384
0x34b655…2a6f
4 touches
1 conflict
0xea1d91a3…b583
0x34b655…2a6f
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x253fa02e…9747
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0003
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0000
0x33a247…6221
2 touches
0 conflicts
0x94873e2b…9de1
0x33a247…6221
2 touches
0 conflicts
0xa18c25a7…775d
0x33a247…6221
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
0xdae0fba130…66c384
Audit this contract →
← previous block
·
next block →
recent activity