pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,105,131
← previous block
next block →
recent activity
Analyzing
Block #85,105,131
13 transactions · 10 stateful · 2026-07-02 11:41:51 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,105,131
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x957d4ba0
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0xed82b078
#7
0x6a464ef7
#8
setData
#9
0x16b373…281b
#10
0x1d69a2…5dc4
#11
execOrders
#12
0xc7e3ec2c
#2
0x957d4ba0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10a2bd5d…ad6d
0x8d1565…6723
4 touches
1 conflict
0x00000000…000a
0x90c374…be45
4 touches
1 conflict
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x34443913…cbf3
0x336ed4…c59c
4 touches
1 conflict
0x47d4745e…02bb
0x336ed4…c59c
4 touches
1 conflict
0x93c58e4d…9b32
0x336ed4…c59c
4 touches
1 conflict
0x006e55b1…660f
0x8d1565…6723
4 touches
1 conflict
0x085c9fac…8fcf
0x8d1565…6723
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:
0x8d156514…236723
1 conflict on slot
0x10a2bd5d43…51ad6d
Audit this contract →
← previous block
·
next block →
recent activity