pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,058,027
← previous block
next block →
recent activity
Analyzing
Block #87,058,027
10 transactions · 10 stateful · 2026-07-11 12:55:23 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,058,027
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x0c7abd22
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
· blocks 2
#9
setData
#7
0x0f6795d9
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x198bae6a…f31c
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2003d8cf…6836
0x34b655…2a6f
4 touches
1 conflict
0xb1e4ea6c…3e29
0x34b655…2a6f
4 touches
1 conflict
0xb588751f…cb86
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd94ac4d1…edb0
0x34b655…2a6f
4 touches
1 conflict
0xd94ac4d1…edb1
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
1 conflict on slot
0x198bae6a2b…20f31c
Audit this contract →
← previous block
·
next block →
recent activity