pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,772,145
← previous block
next block →
recent activity
Analyzing
Block #86,772,145
9 transactions · 5 stateful · 2026-07-10 05:04:47 UTC
Parallelism
78
/100
Blocked
20
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,772,145
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x8263f5d9
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
setData
#7
0x7db443…a178
#8
0x39435dac
#5
0x0f6795d9
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
0x5d74c621…4f44
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0682a731…d1e7
0x34b655…2a6f
2 touches
0 conflicts
0x09499f74…9e08
0x34b655…2a6f
2 touches
0 conflicts
0x0fa79b4e…9c80
0x34b655…2a6f
2 touches
0 conflicts
0x1299b030…e115
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
0x5d74c62121…154f44
Audit this contract →
← previous block
·
next block →
recent activity