pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,417,457
← previous block
next block →
recent activity
Analyzing
Block #71,417,457
10 transactions · 8 stateful · 2026-04-30 01:53:09 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,417,457
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
0x6df9e92b
· blocks 2
#8
setData
#9
0x39435dac
#6
0x6df9e92b
· blocks 1
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xaadf42dc…f433
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x7d0364…a52b
6 touches
3 conflicts
0x00000000…0001
0x7d0364…a52b
6 touches
3 conflicts
0x131ec7f4…baaf
0xaca864…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0xaca864…7777
6 touches
3 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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
3 conflicts on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity