pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,224,271
← previous block
next block →
recent activity
Analyzing
Block #72,224,271
9 transactions · 8 stateful · 2026-05-03 19:32:14 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,224,271
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6943a490
#2
0x98717539
#3
setData
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
0x69f7a336
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65e795ca…0320
0x34b655…2a6f
4 touches
1 conflict
0xc7f28b7a…5777
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0624466c…833e
0x065c9d…c394
2 touches
0 conflicts
0x2700abe0…293b
0x065c9d…c394
2 touches
0 conflicts
0x27f32b4e…b25e
0x065c9d…c394
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
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
0x65e795ca62…450320
Audit this contract →
← previous block
·
next block →
recent activity