pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,773,820
← previous block
next block →
recent activity
Analyzing
Block #90,773,820
10 transactions · 10 stateful · 2026-07-27 12:39:03 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,773,820
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
#3
0x94defb17
· blocks 1
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0xe9316489
#8
setData
#9
0xc7e3ec2c
#4
0x94defb17
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
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x301f96c7…1ef5
0x7b9256…1fb2
4 touches
1 conflict
0x301f96c7…1ef6
0x7b9256…1fb2
4 touches
1 conflict
0x301f96c7…1ef7
0x7b9256…1fb2
4 touches
1 conflict
0xa98ddf61…6732
0x7b9256…1fb2
4 touches
1 conflict
0xa98ddf61…6733
0x7b9256…1fb2
4 touches
1 conflict
0xa98ddf61…6736
0x7b9256…1fb2
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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:
0x7b9256fd…e21fb2
1 conflict on slot
0x0000000000…000006
Audit this contract →
← previous block
·
next block →
recent activity