pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,235,153
← previous block
next block →
recent activity
Analyzing
Block #90,235,153
12 transactions · 11 stateful · 2026-07-25 15:14:22 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,235,153
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
0x0f6795d9
· blocks 1
#3
0x3f5c179b
#4
0x3f5c179b
#5
0x0f6795d9
#7
0x0f6795d9
#8
0x36f359b0
#9
transfer
#10
setData
#11
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x410c23da…5793
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x05e1eba1…6491
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x18e86f02…fa98
0x34b655…2a6f
2 touches
0 conflicts
0x20081203…b191
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
0x410c23dad5…765793
Audit this contract →
← previous block
·
next block →
recent activity