pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,771,276
← previous block
next block →
recent activity
Analyzing
Block #89,771,276
11 transactions · 10 stateful · 2026-07-24 00:14:07 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,771,276
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
exec
#3
0x6ad2e98b
· blocks 1
#5
execFwdPositionOps
· blocks 1
#7
updatePosition
#8
0x6a62aec7
#9
setData
#10
execOrders
#4
0xab083028
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0036
0x386489…7508
2 touches
0 conflicts
0x1a920eda…bfae
0x386489…7508
2 touches
0 conflicts
0x00000000…0036
0x39f901…6bdf
2 touches
0 conflicts
0xc5819118…1448
0x39f901…6bdf
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity