pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#72,971,933
← previous block
next block →
recent activity
Analyzing
Block #72,971,933
12 transactions · 11 stateful · 2026-05-07 06:37:42 UTC
Parallelism
75
/100
Blocked
18
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,971,933
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69fc33ad
#2
forward
#3
updateDataFeedsValuesPartial
#4
0x69fc33ad
#5
0xeffdedb0
#6
setData
#7
execOrders
· blocks 2
#9
execOrders
#11
execOrders
#8
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd11dc26e…59ab
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x3559dd77…dc10
0x34b655…2a6f
2 touches
0 conflicts
0x3b8ffd61…f3ad
0x34b655…2a6f
2 touches
0 conflicts
0x4546ebad…b908
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity