pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,421,071
← previous block
next block →
recent activity
Analyzing
Block #71,421,071
10 transactions · 9 stateful · 2026-04-30 02:17:09 UTC
Parallelism
70
/100
Blocked
44
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,421,071
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
· blocks 3
#3
0x3f5c179b
#4
0x6df9e92b
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#2
0x98717539
#5
0x6df9e92b
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ae
0x8d66a4…3095
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
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
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
3 conflicts on slot
0x676f9f01ee…dea8ac
Audit this contract →
← previous block
·
next block →
recent activity