pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,757,975
← previous block
next block →
recent activity
Analyzing
Block #92,757,975
10 transactions · 8 stateful · 2026-08-03 11:04:12 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,757,975
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x0f6795d9
· blocks 1
#4
0xb2d4797b
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#9
0x59558d29
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49ba8ef6…85ec
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
2 touches
0 conflicts
0x0b2f55fa…9025
0x34b655…2a6f
2 touches
0 conflicts
0x15eb6170…3da3
0x34b655…2a6f
2 touches
0 conflicts
0x1d674032…2e0a
0x34b655…2a6f
2 touches
0 conflicts
0x207e9f25…4724
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
0x49ba8ef607…5485ec
Audit this contract →
← previous block
·
next block →
recent activity