pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,849,536
← previous block
next block →
recent activity
Analyzing
Block #89,849,536
8 transactions · 8 stateful · 2026-07-24 06:49:02 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,849,536
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x785f5745
#2
execFwdPositionOps
· blocks 1
#4
relay
#5
execOrders
#6
0x6a630b55
#7
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x2402e0a6…35f2
0x34b655…2a6f
3 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x1d73754c…2e95
0x34b655…2a6f
2 touches
0 conflicts
0x23e706b3…0e16
0x34b655…2a6f
2 touches
0 conflicts
0x32646adf…e05d
0x34b655…2a6f
2 touches
0 conflicts
0x36f22293…8cf2
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
0x9a3068dd84…9918f0
Audit this contract →
← previous block
·
next block →
recent activity