pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,499,346
← previous block
next block →
recent activity
Analyzing
Block #90,499,346
7 transactions · 6 stateful · 2026-07-26 13:38:18 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,499,346
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x5a5d9a99
#4
0x0f6795d9
· blocks 1
#6
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xffcb5f20…df5a
0x34b655…2a6f
4 touches
1 conflict
0x3d15edcb…8ef6
0x34b655…2a6f
4 touches
1 conflict
0x7c9a221a…782b
0x34b655…2a6f
4 touches
1 conflict
0x0a39a130…3a0f
0x34b655…2a6f
2 touches
0 conflicts
0x1c255c26…11dd
0x34b655…2a6f
2 touches
0 conflicts
0x1eb4e07b…edbf
0x34b655…2a6f
2 touches
0 conflicts
0x279c9c01…c69d
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
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity