pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,040,167
← previous block
next block →
recent activity
Analyzing
Block #90,040,167
13 transactions · 12 stateful · 2026-07-24 22:48:38 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,040,167
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
setData
#4
execFwdPositionOps
#5
execOrders
#6
execOrders
#7
execOrders
· blocks 1
#8
execOrders
· blocks 1
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5908184…0fef
0x34b655…2a6f
4 touches
1 conflict
0xb5cddf91…0abf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x1e96394d…56c5
0x34b655…2a6f
2 touches
0 conflicts
0x3661f59a…874a
0x34b655…2a6f
2 touches
0 conflicts
0x3a09154b…27de
0x34b655…2a6f
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
0xa5908184d7…470fef
Audit this contract →
← previous block
·
next block →
recent activity