pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,990,484
← previous block
next block →
recent activity
Analyzing
Block #90,990,484
10 transactions · 10 stateful · 2026-07-28 06:49:12 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,990,484
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 2
#4
execFwdPositionOps
#5
executeBatch
#8
0x6a685160
#9
setData
#6
execFwdPositionOps
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8eae8a3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x04f6d949…d859
0x34b655…2a6f
2 touches
0 conflicts
0x2af40e42…7a5c
0x34b655…2a6f
2 touches
0 conflicts
0x312c6e56…3d7a
0x34b655…2a6f
2 touches
0 conflicts
0x31f21f79…f045
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
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
0xe8eae8a323…64bacc
Audit this contract →
← previous block
·
next block →
recent activity