pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,825,616
← previous block
next block →
recent activity
Analyzing
Block #90,825,616
9 transactions · 7 stateful · 2026-07-27 16:59:45 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,825,616
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0xc5a04723
#6
0x6a678ef9
#7
setData
#8
execOrders
#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
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x2790db74…b0b2
0x34b655…2a6f
4 touches
1 conflict
0x749a4cb2…15f8
0x34b655…2a6f
4 touches
1 conflict
0x01a08f7d…dec6
0x34b655…2a6f
2 touches
0 conflicts
0x10b7971b…3ba4
0x34b655…2a6f
2 touches
0 conflicts
0x1dd68810…d641
0x34b655…2a6f
2 touches
0 conflicts
0x20ff72d4…5971
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
0x0f2d78b1bb…5e7363
Audit this contract →
← previous block
·
next block →
recent activity