pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,708,431
← previous block
next block →
recent activity
Analyzing
Block #89,708,431
10 transactions · 10 stateful · 2026-07-23 18:56:45 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,708,431
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#3
0x5a5d9a99
· blocks 1
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#7
setData
#8
execOrders
· blocks 1
#2
execute
#6
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
5
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xb5a3b1be…8122
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeaced15b…2221
0x754704…b603
4 touches
1 conflict
0x3c0c2f32…c3df
0x34b655…2a6f
2 touches
0 conflicts
0x3dcbc94a…a380
0x34b655…2a6f
2 touches
0 conflicts
0x506e4e56…ca27
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity