pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,127,018
← previous block
next block →
recent activity
Analyzing
Block #90,127,018
6 transactions · 6 stateful · 2026-07-25 06:09:19 UTC
Parallelism
50
/100
Blocked
33
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,127,018
· 6 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 2
#5
setData
#3
0x0f6795d9
· blocks 1
#4
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4b5e4ba…bce9
0x34b655…2a6f
6 touches
3 conflicts
0xc401f9cb…15e0
0x34b655…2a6f
4 touches
1 conflict
0x544474d6…71b4
0x34b655…2a6f
4 touches
1 conflict
0x1a9064c9…c8ca
0x34b655…2a6f
2 touches
0 conflicts
0x1cdf1b48…9f5e
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6213
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6214
0x34b655…2a6f
2 touches
0 conflicts
0x22af2208…099e
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
3 conflicts on slot
0xc4b5e4baa3…29bce9
Audit this contract →
← previous block
·
next block →
recent activity