pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,421,720
← previous block
next block →
recent activity
Analyzing
Block #71,421,720
9 transactions · 8 stateful · 2026-04-30 02:21:32 UTC
Parallelism
44
/100
Blocked
50
%
Avg conflicts / tx
0.78
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,421,720
· 9 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#6
0x6df9e92b
#7
updateDataFeedsValuesPartial
#8
setData
#2
0x0c7abd22
· blocks 2
#3
0x0c7abd22
· blocks 1
#4
0x0c7abd22
· blocks 1
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14cda0e7…4a2f
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xab2a87f1…eb02
0x1b6862…e19c
6 touches
3 conflicts
0xd9b023e7…a696
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
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:
0xd32edf66…9fff58
6 conflicts on slot
0x14cda0e738…cd4a2f
Audit this contract →
← previous block
·
next block →
recent activity