pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,067,832
← previous block
next block →
recent activity
Analyzing
Block #90,067,832
11 transactions · 9 stateful · 2026-07-25 01:08:36 UTC
Parallelism
82
/100
Blocked
33
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,067,832
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
exactInputSingle
#3
0x0f6795d9
· blocks 3
#7
0x316ba5f2
#8
setData
#9
0x39435dac
#10
0x39435dac
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00cd9338…40d2
0x34b655…2a6f
4 touches
1 conflict
0x04e85631…60f8
0x34b655…2a6f
4 touches
1 conflict
0x09a90ed3…6897
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x3a9e59a0…6198
0x34b655…2a6f
4 touches
1 conflict
0x45368f5c…4b7e
0x34b655…2a6f
4 touches
1 conflict
0x630f113e…c9c6
0x34b655…2a6f
4 touches
1 conflict
0x6fe752ed…4d3b
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
0x00cd933805…2240d2
Audit this contract →
← previous block
·
next block →
recent activity