pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,685,424
← previous block
next block →
recent activity
Analyzing
Block #90,685,424
10 transactions · 9 stateful · 2026-07-27 05:14:23 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,685,424
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
execute
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#7
0x3f5c179b
#8
0x6a66e9a6
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x89028e86…6f98
0x34b655…2a6f
4 touches
1 conflict
0xaa9f27b0…9cf2
0x34b655…2a6f
4 touches
1 conflict
0x30a08400…8eb1
0x34b655…2a6f
3 touches
1 conflict
0xe046eb01…bb75
0x34b655…2a6f
3 touches
1 conflict
0x0d7ffd30…27b2
0x34b655…2a6f
2 touches
0 conflicts
0x2130a548…c1de
0x34b655…2a6f
2 touches
0 conflicts
0x43e3decb…be40
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity