pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,285,446
← previous block
next block →
recent activity
Analyzing
Block #90,285,446
10 transactions · 9 stateful · 2026-07-25 19:28:21 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,285,446
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
artefact_keep
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
0x29eed2d3
#7
setData
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadd9c687…1f8b
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x2392d2…795c
2 touches
0 conflicts
0x183585cc…08fa
0x34b655…2a6f
2 touches
0 conflicts
0x1a6ca283…991f
0x34b655…2a6f
2 touches
0 conflicts
0x1ec7ada6…505b
0x34b655…2a6f
2 touches
0 conflicts
0x27754bd4…96ae
0x34b655…2a6f
2 touches
0 conflicts
0x2ecf1f31…9a68
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
0xadd9c68757…a51f8b
Audit this contract →
← previous block
·
next block →
recent activity