pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,530,558
← previous block
next block →
recent activity
Analyzing
Block #90,530,558
11 transactions · 11 stateful · 2026-07-26 16:15:18 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,530,558
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
· blocks 1
#3
updatePrices
#5
transfer
#6
setData
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#10
0x39435dac
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8743e1ba…8331
0x34b655…2a6f
4 touches
1 conflict
0xabd0bcfc…64e2
0x34b655…2a6f
4 touches
1 conflict
0x09396f14…669f
0x34b655…2a6f
2 touches
0 conflicts
0x0ec7fb56…bca1
0x34b655…2a6f
2 touches
0 conflicts
0x1208457e…3e53
0x34b655…2a6f
2 touches
0 conflicts
0x1bb56de3…732e
0x34b655…2a6f
2 touches
0 conflicts
0x21d69308…2852
0x34b655…2a6f
2 touches
0 conflicts
0x295f4514…60de
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
0x8743e1bab8…0a8331
Audit this contract →
← previous block
·
next block →
recent activity