pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,719,756
← previous block
next block →
recent activity
Analyzing
Block #90,719,756
14 transactions · 13 stateful · 2026-07-27 08:07:05 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,719,756
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postStateList
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
updatePrices
· blocks 1
#7
updatePrices
#9
executeBatch
#10
execFwdPositionOps
#11
execFwdPositionOps
#12
forward
#13
setData
#8
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
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
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x4688dd30…ef52
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5e8223c2…c242
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:
0x48cba278…e2b48b
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity