pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,496,804
← previous block
next block →
recent activity
Analyzing
Block #72,496,804
8 transactions · 6 stateful · 2026-05-05 01:51:58 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,496,804
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xd10227eb
#3
forward
#4
updateTemporalNumericValuesV1
#5
setData
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1347c219…2e22
0xacc0a0…fd62
2 touches
0 conflicts
0x5250d39b…c3fb
0xacc0a0…fd62
2 touches
0 conflicts
0x99b58f4d…a3a2
0xacc0a0…fd62
2 touches
0 conflicts
0xb3b3d607…a990
0xacc0a0…fd62
2 touches
0 conflicts
0xb4bd57ff…3bfd
0xacc0a0…fd62
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
0x109d8a5293…02a7b7
Audit this contract →
← previous block
·
next block →
recent activity