pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,232,965
← previous block
next block →
recent activity
Analyzing
Block #90,232,965
7 transactions · 7 stateful · 2026-07-25 15:03:21 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,232,965
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
approve
#5
0x0f6795d9
#6
setData
#2
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a1643e3…e20d
0x34b655…2a6f
2 touches
0 conflicts
0x18316bb4…d507
0x34b655…2a6f
2 touches
0 conflicts
0x2e9f90bb…9306
0x34b655…2a6f
2 touches
0 conflicts
0x30e0b690…24c2
0x34b655…2a6f
2 touches
0 conflicts
0x41c60d1a…8136
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
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity