pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,264,596
← previous block
next block →
recent activity
Analyzing
Block #87,264,596
10 transactions · 9 stateful · 2026-07-12 11:56:40 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
#87,264,596
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
deposit
#5
0x0f6795d9
· blocks 1
#7
0x0f6795d9
#8
setData
#9
0xc7e3ec2c
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0xa7ff65b9…8e90
0x34b655…2a6f
4 touches
1 conflict
0xbaf991af…3033
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0003
0x0c65a0…0852
2 touches
0 conflicts
0x52c63247…ce02
0x0c65a0…0852
2 touches
0 conflicts
0xb54cbb44…3f40
0x0c65a0…0852
2 touches
0 conflicts
0x0c3b0edd…f7c7
0x34b655…2a6f
2 touches
0 conflicts
0x38bcfe5f…6c71
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
0x31519d107d…60f76b
Audit this contract →
← previous block
·
next block →
recent activity