pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,548,096
← previous block
next block →
recent activity
Analyzing
Block #96,548,096
11 transactions · 11 stateful · 2026-08-16 17:21:48 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,548,096
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#2
execute302
#3
0xab083028
#5
updatePrices
#7
execFwdPositionOpsV2
#8
setData
#9
execFwdPositionOpsV2
#10
proposeResolution
#4
execOrders
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ed92fa9…1d7e
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x6ac4a9ce…5f63
0x34b655…2a6f
4 touches
1 conflict
0x52c63247…ce02
0x0a3323…0a3c
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
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
3 conflicts on slot
0x7ed92fa9c4…fa1d7e
Audit this contract →
← previous block
·
next block →
recent activity