pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,721,578
← previous block
next block →
recent activity
Analyzing
Block #90,721,578
9 transactions · 9 stateful · 2026-07-27 08:16:15 UTC
Parallelism
56
/100
Blocked
33
%
Avg conflicts / tx
0.44
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,721,578
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#3
0x3f5c179b
#6
forward
#7
0x6a671447
#8
setData
#2
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0494220d…abf7
0x34b655…2a6f
4 touches
1 conflict
0xe8d58d34…426d
0x34b655…2a6f
4 touches
1 conflict
0x0494220d…abf6
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x16891dd2…6254
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity