pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#72,973,141
← previous block
next block →
recent activity
Analyzing
Block #72,973,141
10 transactions · 8 stateful · 2026-05-07 06:45:43 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,973,141
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69fc358f
#2
0x98717539
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x69fc358f
#9
0xeffdedb0
#3
0x98717539
· blocks 1
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x336241b2…c1db
0x34b655…2a6f
2 touches
0 conflicts
0x43b339d9…fef6
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity