pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,235,453
← previous block
next block →
recent activity
Analyzing
Block #90,235,453
10 transactions · 9 stateful · 2026-07-25 15:15:53 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,235,453
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#4
updatePriceFeedsIfNecessary
#5
0xc5a04723
#6
0x36f359b0
#7
0x6a64d3a1
#8
transfer
#9
setData
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x13023a6e…25d5
0x34b655…2a6f
2 touches
0 conflicts
0x3260c88b…0e32
0x34b655…2a6f
2 touches
0 conflicts
0x330df1e6…7586
0x34b655…2a6f
2 touches
0 conflicts
0x330df1e6…7587
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
0x80398c66c8…7ef3cc
Audit this contract →
← previous block
·
next block →
recent activity