pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#72,972,823
← previous block
next block →
recent activity
Analyzing
Block #72,972,823
12 transactions · 11 stateful · 2026-05-07 06:43:37 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,972,823
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x9036287a
#4
addLiquidity
#5
updateDataFeedsValuesPartial
#6
0x69fc3510
#7
0xeffdedb0
#8
setData
#9
execOrders
· blocks 1
#11
0x42dd8743
#2
0x0c7abd22
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee110ef…8394
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x94a3fb3f…7515
0x34b655…2a6f
4 touches
1 conflict
0x2529af74…624b
0xd32edf…ff58
3 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x3e04662b…0da7
0x1b6862…e19c
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
0x7ee110efcf…e68394
Audit this contract →
← previous block
·
next block →
recent activity