pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,658,014
← previous block
next block →
recent activity
Analyzing
Block #86,658,014
10 transactions · 5 stateful · 2026-07-09 16:22:36 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,658,014
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
0xabd065…eef5
#5
0x46f9f5…d374
#6
setData
#7
0xdaf002…2ab4
#9
0xc7e3ec2c
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bf5914f…c75d
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xf8478ef9…e6dd
0x34b655…2a6f
4 touches
1 conflict
0x05f3c934…558c
0x34b655…2a6f
2 touches
0 conflicts
0x0c53719e…0366
0x34b655…2a6f
2 touches
0 conflicts
0x10a5a231…be40
0x34b655…2a6f
2 touches
0 conflicts
0x13a79a0a…b414
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
0x2bf5914fac…c4c75d
Audit this contract →
← previous block
·
next block →
recent activity