pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,889,276
← previous block
next block →
recent activity
Analyzing
Block #90,889,276
10 transactions · 9 stateful · 2026-07-27 22:20:01 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,889,276
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x57368ddf
#6
0x94defb17
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0x00d60c65…745d
0x34b655…2a6f
2 touches
0 conflicts
0x15928faa…657d
0x34b655…2a6f
2 touches
0 conflicts
0x171ff85b…255e
0x34b655…2a6f
2 touches
0 conflicts
0x1a137052…e517
0x34b655…2a6f
2 touches
0 conflicts
0x2f0fe1df…da89
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity