pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,256,620
← previous block
next block →
recent activity
Analyzing
Block #91,256,620
13 transactions · 12 stateful · 2026-07-29 05:09:00 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
#91,256,620
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd60faa87
#2
0xab083028
#3
updatePrices
#4
withdraw
#5
updateDataFeedsValuesPartial
#6
batchUpdate
#7
execFwdPositionOps
#8
0x6a698b64
#9
setData
#10
execOrders
· blocks 2
#11
execOrders
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x446f2734…8b54
0x0a3323…0a3c
2 touches
0 conflicts
0xff393f19…4dd2
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0000
0x0d73bf…be07
2 touches
0 conflicts
0x00000000…0001
0x0d73bf…be07
2 touches
0 conflicts
0x00000000…0003
0x0d73bf…be07
2 touches
0 conflicts
0x00000000…000a
0x0d73bf…be07
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity