pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,275,563
← previous block
next block →
recent activity
Analyzing
Block #90,275,563
11 transactions · 11 stateful · 2026-07-25 18:38:07 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,275,563
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#4
0x0f6795d9
#6
execute
#8
0x36f359b0
#9
setData
#10
0x39435dac
#5
0x0f6795d9
· blocks 1
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x16dd4651…e88f
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x3ac99a6c…0433
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x495b950c…7060
0x34b655…2a6f
4 touches
1 conflict
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
0xfa2527aaf5…479dd5
Audit this contract →
← previous block
·
next block →
recent activity