pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,645,281
← previous block
next block →
recent activity
Analyzing
Block #90,645,281
10 transactions · 9 stateful · 2026-07-27 01:52:25 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,645,281
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
0x94defb17
· blocks 1
#6
setData
#7
execOrders
#8
0xc7e3ec2c
#9
0xc7e3ec2c
#5
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ef17495…2358
0x7b9256…1fb2
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x0eb536c7…fa56
0x7b9256…1fb2
4 touches
1 conflict
0x0eb536c7…fa57
0x7b9256…1fb2
4 touches
1 conflict
0x0eb536c7…fa5a
0x7b9256…1fb2
4 touches
1 conflict
0x6ef17495…2357
0x7b9256…1fb2
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
0x6ef1749501…c72358
Audit this contract →
← previous block
·
next block →
recent activity