pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,557,639
← previous block
next block →
recent activity
Analyzing
Block #71,557,639
12 transactions · 9 stateful · 2026-04-30 17:30:47 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,557,639
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
trade
#2
0xa96df62f
#3
0xeffdedb0
#4
0x245845…3a70
#5
0x69f3923e
#6
updateDataFeedsValuesPartial
#7
0x98717539
#8
setData
#9
forward
#10
0x39435dac
· blocks 1
#11
0x39435dac
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
0x109d8a52…a7b7
0x34b655…2a6f
4 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
0x68393815…ea1c
0x2e3234…7d90
2 touches
0 conflicts
0x5e804031…f061
0x73ada1…8be0
2 touches
0 conflicts
0x5e804031…f062
0x73ada1…8be0
2 touches
0 conflicts
0x5e804031…f063
0x73ada1…8be0
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:
0x34b6552d…112a6f
1 conflict on slot
0x109d8a5293…02a7b7
Audit this contract →
← previous block
·
next block →
recent activity