pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,287,196
← previous block
next block →
recent activity
Analyzing
Block #90,287,196
10 transactions · 9 stateful · 2026-07-25 19:37:12 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,287,196
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#4
updatePriceFeedsIfNecessary
#5
executeBatch
#7
0x3f5c179b
#8
0x6a6510df
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0xcb6ad4a1…b1d8
0x34b655…2a6f
4 touches
1 conflict
0xcd597b13…b019
0x34b655…2a6f
4 touches
1 conflict
0xe45796e1…d024
0x34b655…2a6f
4 touches
1 conflict
0xe77c721b…7588
0x34b655…2a6f
4 touches
1 conflict
0xe9457301…83cd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0aeef2b4…12cf
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xfed09e59c7…d6a493
Audit this contract →
← previous block
·
next block →
recent activity