pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,287,765
← previous block
next block →
recent activity
Analyzing
Block #90,287,765
11 transactions · 11 stateful · 2026-07-25 19:40:06 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,287,765
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
artefact_keep
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
0x3f5c179b
#7
handleOps
#8
0x36f359b0
#9
setData
#10
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
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0004
0x23035f…7992
2 touches
0 conflicts
0x226ae29a…2612
0x34b655…2a6f
2 touches
0 conflicts
0x2c390858…b1ed
0x34b655…2a6f
2 touches
0 conflicts
0x2f675ab5…6407
0x34b655…2a6f
2 touches
0 conflicts
0x3387e70b…1967
0x34b655…2a6f
2 touches
0 conflicts
0x5fb3bb71…84b9
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
0x66bdb4c268…a97ea6
Audit this contract →
← previous block
·
next block →
recent activity