pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,036,146
← previous block
next block →
recent activity
Analyzing
Block #90,036,146
9 transactions · 9 stateful · 2026-07-24 22:28:20 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,036,146
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#7
setData
#8
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0fb9e50c…1a35
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xb0a603a9…b126
0x188d58…ea8e
2 touches
0 conflicts
0x22af2208…099e
0x34b655…2a6f
2 touches
0 conflicts
0x4a6982a4…158c
0x34b655…2a6f
2 touches
0 conflicts
0x4c623175…29e4
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
0xf3d10975b0…050d07
Audit this contract →
← previous block
·
next block →
recent activity