pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,386,931
← previous block
next block →
recent activity
Analyzing
Block #90,386,931
10 transactions · 9 stateful · 2026-07-26 04:06:38 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,386,931
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf8047…9385
#2
0x6c05cd2b
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
execFwdPositionOps
· blocks 1
#7
0x6a658846
#8
setData
#9
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf17636eb…d73c
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x7907f7f7…dc3f
0x34b655…2a6f
4 touches
1 conflict
0xa279b18d…63bc
0x34b655…2a6f
4 touches
1 conflict
0xb6fcbbb7…2b31
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
0xf17636ebb8…69d73c
Audit this contract →
← previous block
·
next block →
recent activity