pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,627,376
← previous block
next block →
recent activity
Analyzing
Block #90,627,376
16 transactions · 14 stateful · 2026-07-27 00:22:21 UTC
Parallelism
88
/100
Blocked
7
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,627,376
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
· blocks 1
#3
0xab083028
#5
updateDataFeedsValuesPartial
#6
0x6a66a535
#7
0x62be7533
#8
0x3f5c179b
#9
0x0c7abd22
#10
batchUpdate
#11
execFwdPositionOps
#12
execFwdPositionOps
#13
setData
#14
execOrders
#15
execOrders
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1151b256…b43b
0x09475a…400f
2 touches
0 conflicts
0x3d4d8630…d9e3
0x09475a…400f
2 touches
0 conflicts
0x741048ab…1e62
0x09475a…400f
2 touches
0 conflicts
0xee2e48fa…c427
0x09475a…400f
2 touches
0 conflicts
0x107eeecc…2285
0x607560…d0f5
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:
0x48cba278…e2b48b
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity