pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,070,062
← previous block
next block →
recent activity
Analyzing
Block #90,070,062
11 transactions · 9 stateful · 2026-07-25 01:19:53 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,070,062
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execPerpOps
#3
execPerpOps
#4
execPerpOps
#5
0x5a5d9a99
#6
execFwdPositionOps
· blocks 1
#8
updateDataFeedsValuesPartial
#9
executeBatch
#10
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3111eaa6…ae08
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4f3a6b4a…3819
0x34b655…2a6f
4 touches
1 conflict
0x94de4d05…ad01
0x34b655…2a6f
4 touches
1 conflict
0x66674fc9…8ed7
0x34b655…2a6f
3 touches
1 conflict
0xb57b4bde…7af3
0x34b655…2a6f
3 touches
1 conflict
0x9fd37234…2731
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
0x3111eaa633…9cae08
Audit this contract →
← previous block
·
next block →
recent activity