pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,515,856
← previous block
next block →
recent activity
Analyzing
Block #90,515,856
12 transactions · 8 stateful · 2026-07-26 15:01:21 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,515,856
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
· blocks 1
#8
0xed82b078
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
setData
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16eb5040…a048
0x34b655…2a6f
4 touches
1 conflict
0x8966e74c…f328
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x85e845c1…956a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xde95b18d…3751
0x34b655…2a6f
4 touches
1 conflict
0xea39a150…70a6
0x34b655…2a6f
4 touches
1 conflict
0xea39a150…70a7
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
0x16eb504010…86a048
Audit this contract →
← previous block
·
next block →
recent activity