pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,422,625
← previous block
next block →
recent activity
Analyzing
Block #71,422,625
12 transactions · 11 stateful · 2026-04-30 02:27:34 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,422,625
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0xcf7468f4
#4
0xe7be4706
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
setData
#8
0x366fe5db
#9
forward
#10
0x6df9e92b
· blocks 1
#11
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xaadf42dc…f433
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x7d0364…a52b
4 touches
1 conflict
0x00000000…0001
0x7d0364…a52b
4 touches
1 conflict
0x131ec7f4…baaf
0xaca864…7777
4 touches
1 conflict
0x44ad89ba…cf83
0xaca864…7777
4 touches
1 conflict
0x46cb45de…a567
0x188d58…ea8e
2 touches
0 conflicts
0x0d0b2509…074d
0x3bd359…433a
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:
0x3bd359c1…15433a
1 conflict on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity