pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,847,468
← previous block
next block →
recent activity
Analyzing
Block #89,847,468
9 transactions · 7 stateful · 2026-07-24 06:38:37 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,847,468
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a6308e5
#2
updatePrices
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
· blocks 2
#7
0x39435dac
· blocks 1
#8
0x39435dac
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
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd73f8329…4803
0x34b655…2a6f
4 touches
1 conflict
0xd1dd2e56…48f2
0x34b655…2a6f
3 touches
1 conflict
0x0bcbbcad…fc9c
0x34b655…2a6f
2 touches
0 conflicts
0x0e13682c…b8ad
0x34b655…2a6f
2 touches
0 conflicts
0x1114bab1…2ecd
0x34b655…2a6f
2 touches
0 conflicts
0x159a1084…1341
0x34b655…2a6f
2 touches
0 conflicts
0x193f012e…cde8
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity