pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,329,205
← previous block
next block →
recent activity
Analyzing
Block #90,329,205
10 transactions · 10 stateful · 2026-07-25 23:10:44 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,329,205
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf47a8bb
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
setData
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x403fb46d…0d5a
0x34b655…2a6f
4 touches
1 conflict
0x403fb46d…0d5b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x6b2ba712…0214
0x34b655…2a6f
2 touches
0 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
2 touches
0 conflicts
0xaa48195d…ffee
0x34b655…2a6f
2 touches
0 conflicts
0x12a9b76e…cb76
0x3bd359…433a
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
0x403fb46d59…590d5a
Audit this contract →
← previous block
·
next block →
recent activity