pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,560,195
← previous block
next block →
recent activity
Analyzing
Block #90,560,195
11 transactions · 11 stateful · 2026-07-26 18:44:23 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,560,195
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
0x3f5c179b
#8
0x6a6655fe
#9
setData
#10
execOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x997d4606…b060
0x34b655…2a6f
4 touches
1 conflict
0x997d4606…b061
0x34b655…2a6f
4 touches
1 conflict
0xa169711f…c7f3
0x34b655…2a6f
4 touches
1 conflict
0xa61cfe45…8694
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc2b37cdc…e470
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xef5959a3…2a2f
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
0x997d460640…52b060
Audit this contract →
← previous block
·
next block →
recent activity