pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,366,012
← previous block
next block →
recent activity
Analyzing
Block #72,366,012
11 transactions · 9 stateful · 2026-05-04 11:20:40 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,366,012
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
0x3f5c179b
· blocks 1
#3
0x6df9e92b
#4
updateDataFeedsValuesPartial
#5
0xed82b078
· blocks 1
#7
0x69f88180
#8
setData
#9
0x39435dac
#10
0x39435dac
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x76cdcdd0…3f23
0x065c9d…c394
4 touches
1 conflict
0x024582ce…e73c
0x34b655…2a6f
2 touches
0 conflicts
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x28a9e0ea…8ea3
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x62bdce0a…e94d
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity