pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,690,890
← previous block
next block →
recent activity
Analyzing
Block #89,690,890
10 transactions · 9 stateful · 2026-07-23 17:28:20 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
#89,690,890
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
poke
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x6a624fac
#6
setData
#7
execute
#9
0xc7e3ec2c
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1cc9519…84c1
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0c314d2e…ef96
0x34b655…2a6f
2 touches
0 conflicts
0x12c4df9a…2e64
0x34b655…2a6f
2 touches
0 conflicts
0x1fd98771…f62e
0x34b655…2a6f
2 touches
0 conflicts
0x21ed3831…61e5
0x34b655…2a6f
2 touches
0 conflicts
0x463bb699…f919
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
0xf1cc9519e3…fe84c1
Audit this contract →
← previous block
·
next block →
recent activity