pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,866,703
← previous block
next block →
recent activity
Analyzing
Block #90,866,703
10 transactions · 8 stateful · 2026-07-27 20:26:29 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,866,703
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execOrders
#8
0x6a67bf6c
#9
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721c
0x34b655…2a6f
4 touches
1 conflict
0x00e2cc9a…61e3
0x34b655…2a6f
2 touches
0 conflicts
0x0258318f…3758
0x34b655…2a6f
2 touches
0 conflicts
0x0270e1bb…39cb
0x34b655…2a6f
2 touches
0 conflicts
0x0de075de…f316
0x34b655…2a6f
2 touches
0 conflicts
0x2549796f…83dd
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
0x14fe1598c8…e5d0ba
Audit this contract →
← previous block
·
next block →
recent activity