pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,509,709
← previous block
next block →
recent activity
Analyzing
Block #90,509,709
8 transactions · 7 stateful · 2026-07-26 14:30:26 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,509,709
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a661a7a
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x016799b3…cbae
0x34b655…2a6f
4 touches
1 conflict
0xfc4fcaeb…022c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0bee8017…c90a
0x34b655…2a6f
2 touches
0 conflicts
0x172b2494…0d57
0x34b655…2a6f
2 touches
0 conflicts
0x181ad9cf…26f4
0x34b655…2a6f
2 touches
0 conflicts
0x3d7c8b39…81f9
0x34b655…2a6f
2 touches
0 conflicts
0x495f2eb1…7b0a
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
0x016799b37a…0dcbae
Audit this contract →
← previous block
·
next block →
recent activity