pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,437,780
← previous block
next block →
recent activity
Analyzing
Block #90,437,780
10 transactions · 10 stateful · 2026-07-26 08:28:03 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,437,780
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0x39435dac
#7
updateDataFeedsValuesPartial
#8
0x6a65c58a
#9
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x364289f7…f98a
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x0a906ba5…2454
0x34b655…2a6f
2 touches
0 conflicts
0x1ae19353…cb26
0x34b655…2a6f
2 touches
0 conflicts
0x1ea2b1f6…1d57
0x34b655…2a6f
2 touches
0 conflicts
0x1ea2b1f6…1d58
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
0x364289f709…c1f98a
Audit this contract →
← previous block
·
next block →
recent activity