pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,579,164
← previous block
next block →
recent activity
Analyzing
Block #89,579,164
13 transactions · 13 stateful · 2026-07-23 05:56:59 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,579,164
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
airdrop
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
· blocks 1
#8
0x0f6795d9
#9
batchUpdate
#10
0x6a61ada2
#11
setData
#12
0xc7e3ec2c
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1a4179d3…0f26
0x068f22…7908
2 touches
0 conflicts
0xf0cb663a…2ebe
0x09475a…400f
2 touches
0 conflicts
0x0921c970…9f93
0x34b655…2a6f
2 touches
0 conflicts
0x2d7b3d63…c856
0x34b655…2a6f
2 touches
0 conflicts
0x5eed8370…d27c
0x754704…b603
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:
Perpl
1 conflict on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity