pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,913,978
← previous block
next block →
recent activity
Analyzing
Block #86,913,978
10 transactions · 7 stateful · 2026-07-10 20:52:50 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,913,978
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
updatePriceFeedsIfNecessary
#7
0x6a515c1a
#8
setData
#9
0xcb5eed…9416
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2efac4f6…3abf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x2bc13458…e6d8
0x34b655…2a6f
2 touches
0 conflicts
0x2bc13458…e6d9
0x34b655…2a6f
2 touches
0 conflicts
0x40287836…2dff
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
0x2efac4f6c8…eb3abf
Audit this contract →
← previous block
·
next block →
recent activity