pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,880,249
← previous block
next block →
recent activity
Analyzing
Block #90,880,249
9 transactions · 8 stateful · 2026-07-27 21:34:36 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,880,249
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 2
#5
executeBatch
#8
setData
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x2549796f…83dd
0x34b655…2a6f
4 touches
1 conflict
0x2991946f…45cd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf090a80…4536
0x34b655…2a6f
4 touches
1 conflict
0x471515c5…322a
0x34b655…2a6f
4 touches
1 conflict
0x471515c5…322b
0x34b655…2a6f
4 touches
1 conflict
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
0x81561f70ba…26fefd
Audit this contract →
← previous block
·
next block →
recent activity