pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,811,473
← previous block
next block →
recent activity
Analyzing
Block #90,811,473
12 transactions · 9 stateful · 2026-07-27 15:48:35 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,811,473
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
executeBatch
· blocks 2
#9
0x0f6795d9
#10
setData
#11
0x9b8b55…bbc7
#7
executeBatch
· blocks 1
#8
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x058e9f76…db63
0xe52b14…7230
5 touches
3 conflicts
0x3cebc8f1…975c
0xe52b14…7230
4 touches
1 conflict
0x693b762e…1fcd
0xe52b14…7230
4 touches
1 conflict
0x6a3749da…c493
0xe52b14…7230
4 touches
1 conflict
0x6ad5feb6…5606
0xe52b14…7230
4 touches
1 conflict
0xc4a2f619…eb38
0xe52b14…7230
4 touches
1 conflict
0xd4e69a1d…6139
0xe52b14…7230
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:
0xe52b1424…bb7230
3 conflicts on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity