pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,978,994
← previous block
next block →
recent activity
Analyzing
Block #90,978,994
8 transactions · 6 stateful · 2026-07-28 05:51:20 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,978,994
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#7
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
0xd2d3fe13…b828
0x34b655…2a6f
4 touches
1 conflict
0x81358e16…05df
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb65441ef…8dd8
0x34b655…2a6f
4 touches
1 conflict
0xbc2d4622…e7e9
0x34b655…2a6f
4 touches
1 conflict
0xbe581d31…e0b9
0x34b655…2a6f
4 touches
1 conflict
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
0xd2d3fe1336…0db828
Audit this contract →
← previous block
·
next block →
recent activity