pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,314,644
← previous block
next block →
recent activity
Analyzing
Block #87,314,644
12 transactions · 10 stateful · 2026-07-12 17:31:18 UTC
Parallelism
83
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,314,644
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#7
execute
· blocks 1
#8
execFwdPositionOps
#9
0x6a53cfde
#10
setData
#5
execFwdPositionOps
#6
execOrders
#11
0xb8024e52
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w1
7
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x788e0641…cb8e
0xbaba08…5eb1
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0xc7461450…e1b3
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xc8a96c…aa56
4 touches
1 conflict
0x00000000…0003
0xc8a96c…aa56
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
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
0x0000000000…0000c9
Audit this contract →
← previous block
·
next block →
recent activity