pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,448,495
← previous block
next block →
recent activity
Analyzing
Block #86,448,495
9 transactions · 7 stateful · 2026-07-08 16:59:22 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,448,495
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x0f6795d9
#6
0x0f6795d9
#7
setData
#8
0x97d00b…37fd
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x1b8584fa…730c
0x34b655…2a6f
2 touches
0 conflicts
0x24035043…cb28
0x34b655…2a6f
2 touches
0 conflicts
0x305b535d…c175
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5317
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
0x4ec9ff52ce…67e6f7
Audit this contract →
← previous block
·
next block →
recent activity