pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,677,505
← previous block
next block →
recent activity
Analyzing
Block #89,677,505
10 transactions · 9 stateful · 2026-07-23 16:20:49 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
#89,677,505
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x29eed2d3
#7
setData
#8
0x885f64…3d3e
#9
0x39435dac
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x03a83226…8635
0x065c9d…c394
2 touches
0 conflicts
0x64b7484c…d2fe
0x065c9d…c394
2 touches
0 conflicts
0x82cb1bfc…7a4c
0x065c9d…c394
2 touches
0 conflicts
0xa4f80979…4d71
0x065c9d…c394
2 touches
0 conflicts
0xd35bb5ac…3586
0x065c9d…c394
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:
0x48cba278…e2b48b
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity