pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,429,663
← previous block
next block →
recent activity
Analyzing
Block #72,429,663
8 transactions · 6 stateful · 2026-05-04 18:24:50 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,429,663
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x719d975a
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
setData
#7
0x39435dac
#3
0x13572d0b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3de215fe…c018
0x3bd359…433a
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x00000000…0002
0xbab229…9388
4 touches
1 conflict
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0x00000000…0000
0xbeafc7…6b9e
4 touches
1 conflict
0x00000000…0002
0xbeafc7…6b9e
4 touches
1 conflict
0x00000000…0004
0xbeafc7…6b9e
4 touches
1 conflict
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:
0x3bd359c1…15433a
1 conflict on slot
0x3de215fe7e…e9c018
Audit this contract →
← previous block
·
next block →
recent activity