pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,556,709
← previous block
next block →
recent activity
Analyzing
Block #90,556,709
10 transactions · 9 stateful · 2026-07-26 18:26:50 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
#90,556,709
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
· blocks 1
#3
0x5a5d9a99
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#8
0x57368ddf
#9
setData
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x19b4e3fd…3821
0x34b655…2a6f
2 touches
0 conflicts
0x3347cbe5…846c
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x41d39318…d624
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity