pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,697,506
← previous block
next block →
recent activity
Analyzing
Block #73,697,506
10 transactions · 9 stateful · 2026-05-10 15:11:37 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,697,506
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a00a0a1
#2
0x39435dac
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x5339c59f
· blocks 1
#8
setData
#7
0xed82b078
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w0
7
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2438038…5fa7
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x22863bf9…19df
0x34b655…2a6f
2 touches
0 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x44039c64…0de6
0x34b655…2a6f
2 touches
0 conflicts
0x50c2960c…5f37
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:
0x34b6552d…112a6f
1 conflict on slot
0xf2438038b6…475fa7
Audit this contract →
← previous block
·
next block →
recent activity