pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,890,408
← previous block
next block →
recent activity
Analyzing
Block #90,890,408
9 transactions · 9 stateful · 2026-07-27 22:25:43 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,890,408
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketSell
· blocks 2
#7
forward
#8
setData
#5
placeAndExecuteMarketBuy
· blocks 1
#6
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x0ad498e6…d301
0x851145…3f07
4 touches
1 conflict
0xd537abd7…104a
0x851145…3f07
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x39977254…07b1
0x2b46c0…1669
2 touches
0 conflicts
0x3a3e7727…36c5
0x2b46c0…1669
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:
0x01bff417…bc1071
3 conflicts on slot
0x11b69a7ea1…83334e
Audit this contract →
← previous block
·
next block →
recent activity