pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,361,387
← previous block
next block →
recent activity
Analyzing
Block #87,361,387
11 transactions · 11 stateful · 2026-07-12 22:43:52 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,361,387
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
execFwdPositionOps
#8
0x6a54191f
#9
setData
#10
execOrders
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1526b11f…8b21
0x34b655…2a6f
2 touches
0 conflicts
0x172b0de5…980b
0x34b655…2a6f
2 touches
0 conflicts
0x58cec012…dcb8
0x34b655…2a6f
2 touches
0 conflicts
0x94e7f277…471b
0x34b655…2a6f
2 touches
0 conflicts
0x9ad0eb5b…7a1b
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
0xfaef08b108…f90696
Audit this contract →
← previous block
·
next block →
recent activity