pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,639,391
← previous block
next block →
recent activity
Analyzing
Block #90,639,391
8 transactions · 8 stateful · 2026-07-27 01:22:48 UTC
Parallelism
63
/100
Blocked
38
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,639,391
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 1
#2
execFwdPositionOps
· blocks 2
#6
0x6a66b35f
#7
setData
#3
execFwdPositionOps
· blocks 1
#5
0x42bbae7a
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62a3f11b…03ec
0x34b655…2a6f
4 touches
1 conflict
0x3e0065ad…e39b
0x34b655…2a6f
4 touches
1 conflict
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x26d1c221…4d2a
0x34b655…2a6f
2 touches
0 conflicts
0x2d327a2e…cbff
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
0x62a3f11b78…4b03ec
Audit this contract →
← previous block
·
next block →
recent activity