pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,592,670
← previous block
next block →
recent activity
Analyzing
Block #87,592,670
10 transactions · 10 stateful · 2026-07-14 00:31:28 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,592,670
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0xab083028
#3
execOrders
#4
0x5a5d9a99
· blocks 1
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
0x6a5583d7
#9
setData
#5
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0xb2912a93…235f
0x34b655…2a6f
4 touches
1 conflict
0xd2453506…54e4
0x34b655…2a6f
4 touches
1 conflict
0xd7ce439b…e40d
0x34b655…2a6f
4 touches
1 conflict
0xe5b1f066…4362
0x34b655…2a6f
4 touches
1 conflict
0xf5480ced…7011
0x34b655…2a6f
4 touches
1 conflict
0x17cc5ec3…ae0e
0x34b655…2a6f
4 touches
1 conflict
0x21158693…63e2
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: Settlement / Helper
1 conflict on slot
0x5170a2184f…f03a84
Audit this contract →
← previous block
·
next block →
recent activity