pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,150,969
← previous block
next block →
recent activity
Analyzing
Block #91,150,969
12 transactions · 12 stateful · 2026-07-28 20:17:27 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,150,969
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x6a690ecf
#5
setData
#6
0x0f6795d9
#7
0x94defb17
· blocks 1
#9
0x0f6795d9
#10
0x59558d29
#11
0xc7e3ec2c
#8
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0xcd9fda0f…d877
0x7b9256…1fb2
4 touches
1 conflict
0xcd9fda0f…d878
0x7b9256…1fb2
4 touches
1 conflict
0xcd9fda0f…d879
0x7b9256…1fb2
4 touches
1 conflict
0xdffd9dab…eb35
0x7b9256…1fb2
4 touches
1 conflict
0xdffd9dab…eb36
0x7b9256…1fb2
4 touches
1 conflict
0xdffd9dab…eb39
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:
USDC (USDC)
1 conflict on slot
0xe1f61186c5…67e2f8
Audit this contract →
← previous block
·
next block →
recent activity