pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,311,274
← previous block
next block →
recent activity
Analyzing
Block #90,311,274
11 transactions · 9 stateful · 2026-07-25 21:39:37 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,311,274
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#7
0x6a652d91
#8
setData
#9
execOrders
#10
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8f63f383…6eda
0x34b655…2a6f
4 touches
1 conflict
0x0f82dba2…24d6
0x34b655…2a6f
2 touches
0 conflicts
0x12bc23cf…d56d
0x34b655…2a6f
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x6b2ba712…0214
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity