pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,420,767
← previous block
next block →
recent activity
Analyzing
Block #71,420,767
10 transactions · 9 stateful · 2026-04-30 02:15:06 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,420,767
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
claim
· blocks 1
#7
claim
#9
setData
#2
_makeSwaps
· blocks 1
#8
claim
#3
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0x544ac270…ab6b
0x3bd359…433a
4 touches
1 conflict
0x890f72c6…686a
0xa6afd3…d132
3 touches
1 conflict
0x3bef5ba7…c227
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
0x00000000…0012
0x1b6862…e19c
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x8876d94c2a…cc8435
Audit this contract →
← previous block
·
next block →
recent activity